2011-08-07 46 views
0

我有一個進程根據發佈的元數據層中的更改動態更改我的SQL2K5表結構。查詢時出現死鎖INFORMATION_SCHEMA

例如,如果一個新的列需要添加和表沒有依賴關係 - 步驟是: 1.使用T-SQL對於任何索引&已經在表中存在主鍵[這些創建腳本腳本包括下面] 2.刪除該表 3.重新創建從具有新列的元層的表 4.執行在步驟#1中 5.創建的腳本使用BulkCopy

填充表

以上是通過.NET程序集啓動的,每天在3個併發流中運行。

我在步驟1中收到死鎖錯誤 - 當我訪問INFORMATION_SCHEMA表格來編制索引/鍵時。我在這些腳本中使用了提示WITH(NOLOCK),認爲這應該可以防止3個這樣的操作併發運行時發生任何鎖定。一個表只能在1個流中處理(創建或腳本)。

還有什麼我需要做的嗎?

任何意見非常感謝。

[腳本]

ALTER Procedure [dbo].[s$spScriptPrimaryKeyForTable] 
@Tablename varchar(100) 
AS 


-- Get all existing primary keys 
DECLARE cPK CURSOR FOR 
SELECT TABLE_NAME, CONSTRAINT_NAME 
FROM INFORMATION_SCHEMA.TABLE_CONSTRAINTS WITH(NOLOCK) 
WHERE upper(TABLE_NAME)=upper(@Tablename) 
ORDER BY TABLE_NAME 

DECLARE @PkTable SYSNAME 
DECLARE @PkName SYSNAME 

-- Loop through all the primary keys 
OPEN cPK 
FETCH NEXT FROM cPK INTO @PkTable, @PkName 
WHILE (@@FETCH_STATUS = 0) 
BEGIN 
DECLARE @PKSQL NVARCHAR(4000) SET @PKSQL = '' 
SET @PKSQL = 'ALTER TABLE ' + @PkTable + ' ADD CONSTRAINT ' + @PkName + ' PRIMARY KEY CLUSTERED (' 

-- Get all columns for the current primary key 
DECLARE cPKColumn CURSOR FOR 
SELECT COLUMN_NAME 
FROM INFORMATION_SCHEMA.KEY_COLUMN_USAGE WITH(NOLOCK) 
WHERE TABLE_NAME = @PkTable AND CONSTRAINT_NAME = @PkName 
ORDER BY ORDINAL_POSITION 
OPEN cPKColumn 

DECLARE @PkColumn SYSNAME 
DECLARE @PkFirstColumn BIT SET @PkFirstColumn = 1 
-- Loop through all columns and append the sql statement 
FETCH NEXT FROM cPKColumn INTO @PkColumn 
WHILE (@@FETCH_STATUS = 0) 
BEGIN 
IF (@PkFirstColumn = 1) 
SET @PkFirstColumn = 0 
ELSE 
SET @PKSQL = @PKSQL + ', ' 

SET @PKSQL = @PKSQL + @PkColumn 

FETCH NEXT FROM cPKColumn INTO @PkColumn 
END 
CLOSE cPKColumn 
DEALLOCATE cPKColumn 

SET @PKSQL = @PKSQL + ')' 
-- Print the primary key statement 
-- PRINT @PKSQL 

FETCH NEXT FROM cPK INTO @PkTable, @PkName 
END 
CLOSE cPK 
DEALLOCATE cPK 


SELECT ISNULL(@PKSQL,' ') 

================ 

ALTER Procedure [dbo].[s$spScriptIndexesForTable] 
@Tablename varchar(100) 

AS 

DECLARE @RetVal varchar(4000) 
SET @RetVal = '' 

-- Get all existing indexes, but NOT the primary keys 
DECLARE cIX CURSOR FOR 
SELECT OBJECT_NAME(SI.Object_ID), SI.Object_ID, SI.Name, SI.Index_ID 
FROM Sys.Indexes SI WITH(NOLOCK) 
LEFT JOIN INFORMATION_SCHEMA.TABLE_CONSTRAINTS TC WITH(NOLOCK) ON SI.Name = TC.CONSTRAINT_NAME AND OBJECT_NAME(SI.Object_ID) = TC.TABLE_NAME 
WHERE TC.CONSTRAINT_NAME IS NULL 
AND OBJECTPROPERTY(SI.Object_ID, 'IsUserTable') = 1 
AND upper(OBJECT_NAME(SI.Object_ID))=upper(@Tablename) 
ORDER BY OBJECT_NAME(SI.Object_ID), SI.Index_ID 

DECLARE @IxTable SYSNAME 
DECLARE @IxTableID INT 
DECLARE @IxName SYSNAME 
DECLARE @IxID INT 

-- Loop through all indexes 
OPEN cIX 
FETCH NEXT FROM cIX INTO @IxTable, @IxTableID, @IxName, @IxID 
WHILE (@@FETCH_STATUS = 0) 
BEGIN 
DECLARE @IXSQL NVARCHAR(4000) 
--SET @PKSQL = '' 
SET @IXSQL = 'CREATE ' 

-- Check if the index is unique 
IF (INDEXPROPERTY(@IxTableID, @IxName, 'IsUnique') = 1) 
SET @IXSQL = @IXSQL + 'UNIQUE ' 
-- Check if the index is clustered 
IF (INDEXPROPERTY(@IxTableID, @IxName, 'IsClustered') = 1) 
SET @IXSQL = @IXSQL + 'CLUSTERED ' 

SET @IXSQL = @IXSQL + 'INDEX ' + @IxName + ' ON [' + @IxTable + '] (' 

-- Get all columns of the index 
DECLARE cIxColumn CURSOR FOR 
SELECT SC.Name,IC.[is_included_column],IC.is_descending_key 
FROM Sys.Index_Columns IC WITH(NOLOCK) 
JOIN Sys.Columns SC WITH(NOLOCK) ON IC.Object_ID = SC.Object_ID AND IC.Column_ID = SC.Column_ID 
WHERE IC.Object_ID = @IxTableID AND Index_ID = @IxID 
ORDER BY IC.Index_Column_ID,IC.is_included_column 

DECLARE @IxColumn SYSNAME 
DECLARE @IxIncl bit 
DECLARE @Desc bit 
DECLARE @IxIsIncl bit set @IxIsIncl = 0 
DECLARE @IxFirstColumn BIT SET @IxFirstColumn = 1 

-- Loop throug all columns of the index and append them to the CREATE statement 
OPEN cIxColumn 
FETCH NEXT FROM cIxColumn INTO @IxColumn, @IxIncl, @Desc 
WHILE (@@FETCH_STATUS = 0) 
BEGIN 

IF (@IxFirstColumn = 1) 
BEGIN 
SET @IxFirstColumn = 0 
END 
ELSE 
BEGIN 
--check to see if it's an included column 
IF ((@IxIsIncl = 0) AND (@IxIncl = 1)) 
BEGIN 
SET @IxIsIncl = 1 
SET @IXSQL = @IXSQL + ') INCLUDE (' 
END 
ELSE 
BEGIN 
SET @IXSQL = @IXSQL + ', ' 
END 
END 

SET @IXSQL = @IXSQL + '[' + @IxColumn + ']' 
--check to see if it's DESC 
IF @Desc = 1 
SET @IXSQL = @IXSQL + ' DESC' 

FETCH NEXT FROM cIxColumn INTO @IxColumn, @IxIncl, @Desc 
END 
CLOSE cIxColumn 
DEALLOCATE cIxColumn 

SET @IXSQL = @IXSQL + ')' 

-- Print out the CREATE statement for the index 
--SELECT 'IXSQL: ' + @IXSQL 
IF @RetVal IS NULL 
SET @RetVal = '' 
--SELECT 'Retval: ' + @RetVal 
SET @RetVal = @RetVal + @IXSQL + ' ' 

FETCH NEXT FROM cIX INTO @IxTable, @IxTableID, @IxName, @IxID 
END 

CLOSE cIX 
DEALLOCATE cIX 

SELECT ISNULL(@RetVal,' ') 
+0

哪個過程導致死鎖,腳本主鍵或編寫腳本索引的過程?你爲什麼使用INFORMATION_SCHEMA,INDEXPROPERTY等代替sys.key_constraints,sys.index_columns,sys.indexes.is_clustered等? –

回答

1
  1. INFORMATION_SCHEMA的意見是 - 觀點。您無法更新它們,因此它們不太可能導致任何死鎖。如果你想確定真正的源代碼(我認爲這與你的修改有關,或者你沒有顯示的遊標中的其他代碼,或者你調用這些程序時調用的其他代碼 - 因爲選擇意見然後選擇變量不能成爲原因),我建議閱讀Gail Shaw's blog post on interpreting deadlocks

  2. 儘管(1)我仍然建議使用比INFORMATION_SCHEMA更現代的目錄視圖。例如,可以從sys.key_constraints中派生出相同的信息。

  3. 您正在使用默認光標選項;你在嵌套遊標。如果最終仍然使用遊標,則應該習慣於使用資源較少的遊標(例如LOCAL STATIC FORWARD_ONLY READ_ONLY)。

  4. 實際上您並不需要光標來執行此操作。下面是我會重新寫的PK表腳本:

    CREATE PROCEDURE dbo.ScriptPKForTable 
        @TableName SYSNAME 
    AS 
    BEGIN 
        SET NOCOUNT ON; 
    
        DECLARE 
         @pkName SYSNAME, 
         @clustered BIT, 
         @object_id INT, 
         @sql  NVARCHAR(MAX); 
    
        SELECT 
         @object_id = OBJECT_ID(UPPER(@TableName)); 
    
        SELECT 
         @pkName = kc.name, 
         @clustered = CASE i.[type] 
         WHEN 1 THEN 1 ELSE 0 END 
        FROM 
         sys.key_constraints AS kc 
        INNER JOIN 
         sys.indexes AS i 
         ON kc.parent_object_id = i.[object_id] 
         AND kc.unique_index_id = i.index_id 
        WHERE 
         kc.parent_object_id = @object_id 
         AND kc.[type] = 'pk'; 
    
        SET @sql = N'ALTER TABLE ' + QUOTENAME(@TableName) 
         + ' ADD CONSTRAINT ' + @pkName 
         + ' PRIMARY KEY ' + CASE @clustered 
         WHEN 1 THEN 'CLUSTERED' ELSE '' END + ' ('; 
    
        SELECT 
         @sql = @sql + c.name + ',' 
        FROM 
         sys.index_columns AS ic 
        INNER JOIN 
         sys.indexes AS i 
         ON ic.index_id = i.index_id 
         AND ic.[object_id] = i.[object_id] 
        INNER JOIN 
         sys.key_constraints AS kc 
         ON i.[object_id] = kc.[parent_object_id] 
         AND kc.unique_index_id = i.index_id 
        INNER JOIN 
         sys.columns AS c 
         ON i.[object_id] = c.[object_id] 
         AND ic.column_id = c.column_id 
        WHERE 
         kc.[type] = 'PK' 
         AND kc.parent_object_id = @object_id 
        ORDER BY key_ordinal; 
    
        SET @sql = LEFT(@sql, LEN(@sql) - 1) + ');'; 
    
        SELECT COALESCE(@sql, ' '); 
    END 
    GO 
    

至於索引創建腳本,我認爲這是一個更好的辦法沒有明確的指針再做一次(,而不是避免光標是目標,但代碼將成爲一個LOT清理器)。首先,你從索引需要一個函數來建立的任一按鍵或包括列:

CREATE FUNCTION dbo.BuildIndexColumns 
(
    @object_id  INT, 
    @index_id   INT, 
    @included_columns BIT 
) 
RETURNS NVARCHAR(MAX) 
AS 
BEGIN 
    DECLARE @s NVARCHAR(MAX); 

    SELECT @s = N''; 

    SELECT @s = @s + c.name + CASE ic.is_descending_key 
    WHEN 1 THEN ' DESC' ELSE '' END + ',' 
    FROM sys.index_columns AS ic 
    INNER JOIN sys.columns AS c 
    ON ic.[object_id] = c.[object_id] 
    AND ic.column_id = c.column_id 
    WHERE c.[object_id] = @object_id 
    AND ic.[object_id] = @object_id 
    AND ic.index_id = @index_id 
    AND ic.is_included_column = @included_columns 
    ORDER BY ic.key_ordinal; 

    IF @s > N'' 
    SET @s = LEFT(@s, LEN(@s)-1); 

    RETURN (NULLIF(@s, N'')); 
END 
GO 

有了這一功能,ScriptIndexes過程是很容易的:

CREATE PROCEDURE dbo.ScriptIndexesForTable 
    @TableName SYSNAME 
AS 
BEGIN 
    SET NOCOUNT ON; 

    DECLARE 
     @sql  NVARCHAR(MAX), 
     @object_id INT; 

    SELECT @sql = N'', @object_id = OBJECT_ID(UPPER(@TableName)); 

    SELECT @sql = @sql + 'CREATE ' 
     + CASE i.is_unique WHEN 1 THEN 'UNIQUE ' ELSE '' END 
     + CASE i.[type] WHEN 1 THEN 'CLUSTERED ' ELSE '' END 
     + ' INDEX ' + i.name + ' ON ' + QUOTENAME(@TableName) + ' (' 
     + dbo.BuildIndexColumns(@object_id, i.index_id, 0) 
     + ')' + COALESCE(' INCLUDE(' 
     + dbo.BuildIndexColumns(@object_id, i.index_id, 1) 
     + ')', '') + ';' + CHAR(13) + CHAR(10) 
    FROM 
     sys.indexes AS i 
    WHERE 
     i.[object_id] = @object_id 
     -- since this will be covered by ScriptPKForTable: 
     AND i.is_primary_key = 0 
    ORDER BY i.index_id; 

    SELECT COALESCE(@sql, ' '); 
END 
GO 

請注意,我的解決方案不承擔PK是聚集的(你的PK腳本是硬編碼的羣集,但是你的索引腳本假設任何索引都可以聚集)。我還忽略了其他屬性,例如文件組,分區或篩選索引(2005年不支持)。

+0

感謝您的意見和腳本亞倫! (我非常希望看到您的索引創建腳本) 錯誤來自腳本編寫過程,而不是創建/更改表 - 如果您確信調用這些視圖不應該有一個影響。 但是,我無法從我的日誌中看出它是否在調用索引或主鍵存儲過程時發生炸彈襲擊。 – simon

+0

當我建立我的CREATE TABLE腳本,我開始用下面的: 「構造SQL TSQL = 「使用[」 &info.SQLServerDestDatabase和 「]」 &vbNewLine TSQL&= 「SET ANSI_NULLS ON」 &vbNewLine TSQL& = 「SET QUOTED_IDENTIFIER ON」 &vbNewLine TSQL&= 「CREATE TABLE [DBO]。[」 &info.SQLServerDestTableName& 「(」 &vbNewLine \t \t ... 我然後用簡單的執行語句: 提供SQLHelper .ExecuteNonQuery(sqlConnString,CommandType.Text,tsql) 有什麼我可以做的,以防止導致到這一點的死鎖? – simon

+0

再一次,我沒有看到任何在你的評論中會大喊「僵局!死鎖!「你必須更準確地把它放下來,而不僅僅是猜測腳本的哪一部分會導致死鎖。在這兩種情況下,你的存儲過程在構建遊標後只是運行一個SELECT,所以它必須是其他地方(我懷疑在你調用過程之後)第一件事就是修復你的遊標...... –