Skip to content

jobbish-sql/SQL-Server-Multi-Thread

master
Switch branches/tags
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 

Splitting up work to run between multiple SQL Server Agent jobs isn't the easiest thing to do. This framework aims to simplify the process by abstracting away the Agent job parts. Currently only supported for Azure SQL Managed Instances and on-premises SQL Server 2016 SP2+, 2017, and 2019.

core

You need the core folder to use any of the code in this repository. This folder contains the stored procedures needed for the Agent job multi-threading framework. Key features:

  • All Agent job work is abstracted away with a parent, child, and cleanup stored procedure model
  • Can specify the maximum number of child stored procedures that can run at the same time
  • The cleanup procedure stops all child procedures if they hit the defined time limit
  • The child procedures reschedule themselves in an attempt to spread out work over schedulers evenly
  • Validation and error reporting

cci_maintenance

You want the cci_maintenance folder if you need a clustered columnstore maintenance solution designed to work over very large databases that gives you full control over what maintenance actions happen. You define the priority order for maintenance actions as well as whether or not a partition should go through REORGANIZE or REBUILD. Key features:

  • Can create multiple threads to do work concurrently
  • Stops all work at time limit
  • Supports columnstore indexes in multiple databases
  • Over 40 data points available to define the priority order at the partition level for maintenance actions
  • Over 40 data points available to choose between REORGANIZE and REBUILD at the partition level
  • Saves history of previous runs which can be used for prioritization
  • Queries against sys.dm_db_column_store_row_group_physical_stats run multi-threaded and are skipped if possible

Note: REORGANIZE and REBUILD do not preserve segment level ordering within a partition. Tables can be excluded from maintenance actions at the schema, table, or table name pattern matching levels. For a maintenance solution that can perserve segment ordering check out CISL.

Install order:

  1. Run script in core/sp_AgentJobMultiThread.sql
  2. Create tables in cci_maintenance/CCI_Reorg_Rebuild_Tables.sql
  3. Run script in cci_maintenance/CCI_Reorg_Rebuild_Code.sql

Example stored procedure call using all default parameter values:

EXEC [dbo].[CCIReorgAndRebuild]
@CCI_included_database_name_list= N'🔥', -- database list with your CCIs
@max_CCI_alter_job_count = 2, -- number of concurrent jobs that can run
@max_minutes_to_run = 60; -- timeout for all jobs

demo

You want the demo folder if you are developing your own code using the framework and think that looking at a simple example would be helpful. This workload runs make-work stored procedures that calculate checksums.

About

A framework to do multi-threading in T-SQL using SQL Server Agent jobs.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Languages