Overcoming Issues with TempDB Contention

One of the possible bottlenecks for a busy SQL Server is contention in TempDB. This symptoms of this bottleneck are mostly excess wait_types of PAGELATCHEX that are blocking one another. (you can use sp_who3 in order to see whether those wait types are popping up during your busy times). The cause of this is either implicit or explicit use of TempDB. Explicit being creation of table variables and temp tables, or implicit being worktables being generated by complex execution plans. Luckily there are a number of steps you can take in order to overcome these issues. 1) Enable traceflag 1118 There is some argument as to whether this trace flag actually makes a difference. first of all, MS SQL CSS engineers state it’s already the default for 2008. What the flag does is immediately allocate space for tempdb tables upon creation rather than on insert (if I understand it correctly). It did seem to help our database during one point of contention, but I’m not willing to test it again by turning it off. So with that said, “it can’t hurt to turn it on” at least that’s that the consensus of what I’ve read. 2) Put TempDB on a PCIE SSD The PCIE cards are getting cheaper every month. Just putting this in, reduced our write speed from 2.3ms to .3ms. What that translates into is, it’s quicker to get “in and out” of tempdb allowing less contention and higher throughput. Also while I’m too lazy to prove it, […] Continue reading ...

CTE’s vs Temp tables – an Opinion

This is one of those topics that will get people fired up. But here goes. I am mostly an explicit temp table developer. By contrast, I am not an implicit temp table developer. What I mean by that is – in writing SQL, you simply cannot avoid the use of tempdb. Either you write to tempdb by breaking queries out and intentionally create temp tables, or you write to tempdb by not breaking queries out (keeping them as long convoluted statements with a long convoluted query plan) and let the optimizer create “worktables”. In either case you are writing to tempdb whether you like it or not. Yet.. the difference is this: Breaking them out: You can control the size of the result set being written to disk You can ensure that the execution plan is simple You can utilize the materialized temp table data throughout the entire procedure Temp tables contain statistics and can be indexed To compare temp table development to CTE development is somewhat of an apples and oranges comparison. A CTE uses nothing special on the back end. It is simply a (potentially) clean way to write a query. The difference is this however. With a CTE, the execution plan of the main query becomes intertwined with the CTE, leaving more room for the optimizer to get confused. By contrast, when a temp table divides two queries, the optimizer is not intertwined with that which created the temp table and the execution plans stay simple and […]

Copy Stored Procedures Between Servers

This procedure will migrate all your stored procedures located on on server to another via linked server. Just specify the linked server name, remote database, and local database. CREATE PROCEDURE [dba].[pr_refresh_create_procedures]     @linked_server VARCHAR(100),     @source_db VARCHAR(100),     @target_db VARCHAR(100) AS --EXEC [dba].[pr_refresh_create_procedures] 'LOCALSERVER', 'yourdbname', 'targetdb_dev' SET @source_db = '[' + @linked_server + '].[' + @source_db + ']'; DECLARE @SQL Nvarchar(MAX) DECLARE @Name VARCHAR(255) = @target_db IF OBJECT_ID(N'dbadmin.tmp.shelldb_copy_procedures') IS NOT NULL DROP TABLE dbadmin.tmp.shelldb_copy_procedures SET @SQL = 'SELECT p.name, m.Definition INTO dbadmin.tmp.shelldb_copy_procedures FROM ' + @source_db + '.sys.objects p WITH (NOLOCK) INNER JOIN ' + @source_db + '.sys.sql_modules m WITH (NOLOCK) ON p.object_id = m.object_id WHERE type IN (''FN'', ''IF'', ''TF'', ''P'', ''V'', ''TT'')' EXEC(@SQL) DECLARE c CURSOR FOR    SELECT Definition    FROM dbadmin.tmp.shelldb_copy_procedures OPEN c FETCH NEXT FROM c INTO @SQL WHILE @@FETCH_STATUS = 0 BEGIN    SET @SQL = REPLACE(@SQL,'''','''''')    SET @SQL = N'execute ' + QUOTENAME(@name) + N'.dbo.sp_executesql N''' + @SQL + ''''    EXEC(@SQL)    FETCH NEXT FROM c INTO @SQL END             CLOSE c DEALLOCATE c Continue reading ...

Copy Table Data Between Servers

This script will copy table data from one environment to another. This script uses a multithreaded clr procedure created by Alan Kaplan here. You can also change the parallel call below if you want to execute serially. CREATE PROCEDURE [dba].[pr_refresh_insert_table_data]     @linked_server VARCHAR(100),     @source_db VARCHAR(100),     @target_db VARCHAR(100) AS -- dba.pr_refresh_insert_table_data '10.10.60.58', 'yourdbname', 'targetdb' -- SELECT * FROM dbadmin.dbo.refresh_table_columns BEGIN     SET NOCOUNT ON;     DECLARE @SQL nvarchar(MAX);     DECLARE @SQLColumnList nvarchar(MAX);     DECLARE @SQLSelectColumnList nvarchar(MAX);     DECLARE @CRLF nvarchar(2);     DECLARE @Tab nvarchar(1);     DECLARE @RecordKeyName nvarchar(50);     DECLARE @TableID INT;     DECLARE @TableCount INT;     DECLARE @SOURCE VARCHAR(MAX) = '[' + @linked_server + '].[' + @source_db + ']'     DECLARE @TableName VARCHAR(255);     SET @TableName = ''; -- Comment out to use list technique below     DECLARE @TableList TABLE (         TableID INT IDENTITY(1, 1) NOT NULL,         TableName VARCHAR(255)         );         DECLARE @InsertData Generic_Tt_VarcharMax_5_Col     INSERT INTO @TableList(TableName)     SELECT DISTINCT TABLE_NAME     FROM DBADMIN.[tmp].[refresh_table_schema_list] tsl     WHERE process_data = 1     AND EXISTS (SELECT 1 FROM dbadmin.tmp.refresh_create_tables WHERE TABLE_NAME = tsl.TABLE_NAME)     SET @CRLF = CHAR(13) + CHAR(10);     SET @Tab = CHAR(9);       SET @TableCount = (SELECT COUNT(1) FROM @TableList);     SET @TableID = 1; DECLARE @has_identity INT     SET @TableID = 1;   […]

Copy Table DDL Between Servers

This script will allow you to specify a linked server name, a remote database on that linked server, and a local database name in which to copy all the tables from on server onto another. CREATE PROCEDURE [dba].[pr_refresh_create_tables]     @linked_server VARCHAR(100),     @source_db VARCHAR(100),     @target_db VARCHAR(100),     @debug_mode INT = 0 AS -- dba.pr_refresh_create_tables '10.10.60.58', 'yourdbname', 'targetdb', 0 -- SELECT * FROM dbadmin.dbo.refresh_table_columns BEGIN     DECLARE @SQL nvarchar(MAX);     DECLARE @SQLColumnList nvarchar(MAX);     DECLARE @SQLSelectColumnList nvarchar(MAX);     DECLARE @CRLF nvarchar(2);     DECLARE @Tab nvarchar(1);     DECLARE @RecordKeyName nvarchar(50);     DECLARE @RecordKeyDataType nvarchar(50);     DECLARE @TableID INT;     DECLARE @TableCount INT;     DECLARE @SOURCE VARCHAR(MAX) = '[' + @linked_server + '].[' + @source_db + ']'     DECLARE @TableName VARCHAR(255);     DECLARE @TableList TABLE (         TableID INT IDENTITY(1, 1) NOT NULL,         TableName VARCHAR(255)         );     IF OBJECT_ID(N'dbadmin.dbo.refresh_table_columns_tmp') IS NOT NULL DROP TABLE dbadmin.dbo.refresh_table_columns_tmp     IF OBJECT_ID(N'dbadmin.dbo.refresh_table_columns') IS NOT NULL DROP TABLE dbadmin.dbo.refresh_table_columns     IF OBJECT_ID(N'dbadmin.tmp.refresh_create_tables') IS NOT NULL DROP TABLE dbadmin.tmp.refresh_create_tables     CREATE TABLE dbadmin.dbo.refresh_table_columns_tmp (         RowID INT NOT NULL,         TableName VARCHAR(255),         ColumnName VARCHAR(255),         IsIdentity bit,         DataType VARCHAR(50),         IsDataTypeCast bit,         IsNullable bit,         IsLast bit       […] Continue reading ...

Featured Articles

 Site Author