禁用外键约束,仍然不能截断表?(SQL Server 2005)

lar*_*ryq 29 sql-server constraints foreign-keys

我有一个名为PX_Child的表,它在PX_Parent上有一个外键.我想暂时禁用此FK约束,以便我可以截断PX_Parent.我不确定这是怎么回事.

我试过这些命令

ALTER TABLE PX_Child NOCHECK CONSTRAINT ALL

ALTER TABLE PX_Parent NOCHECK CONSTRAINT ALL

(truncate commands)

ALTER TABLE PX_Child CHECK CONSTRAINT ALL

ALTER TABLE PX_Parent CHECK CONSTRAINT ALL
Run Code Online (Sandbox Code Playgroud)

但截断仍然告诉我,由于外键约束,它不能截断PX_Parent.我在网上看了一遍,似乎找不到我做错了什么,对不起这个问题的基本性质.

bob*_*obs 41

如果有任何外键引用它,则不能截断表,包括禁用的约束.您可能需要删除外键约束或使用该DELETE命令.


RJB*_*RJB 16

有一种更容易的方式.我面临着同样的问题,发现此解决方案: https://www.mssqltips.com/sqlservertip/3347/drop-and-recreate-all-foreign-key-constraints-in-sql-server/

如果您只是在数据库中运行此查询,它将生成您需要在您的sproc之前/之后包含的T-SQL,以便删除然后恢复任何外键约束.

不要担心尝试理解这个查询本身.

CREATE TABLE #x -- feel free to use a permanent table
(
  drop_script NVARCHAR(MAX),
  create_script NVARCHAR(MAX)
);

DECLARE @drop   NVARCHAR(MAX) = N'',
        @create NVARCHAR(MAX) = N'';

-- drop is easy, just build a simple concatenated list from sys.foreign_keys:
SELECT @drop += N'
ALTER TABLE ' + QUOTENAME(cs.name) + '.' + QUOTENAME(ct.name) 
    + ' DROP CONSTRAINT ' + QUOTENAME(fk.name) + ';'
FROM sys.foreign_keys AS fk
INNER JOIN sys.tables AS ct
  ON fk.parent_object_id = ct.[object_id]
INNER JOIN sys.schemas AS cs 
  ON ct.[schema_id] = cs.[schema_id];

INSERT #x(drop_script) SELECT @drop;

-- create is a little more complex. We need to generate the list of 
-- columns on both sides of the constraint, even though in most cases
-- there is only one column.
SELECT @create += N'
ALTER TABLE ' 
   + QUOTENAME(cs.name) + '.' + QUOTENAME(ct.name) 
   + ' ADD CONSTRAINT ' + QUOTENAME(fk.name) 
   + ' FOREIGN KEY (' + STUFF((SELECT ',' + QUOTENAME(c.name)
   -- get all the columns in the constraint table
    FROM sys.columns AS c 
    INNER JOIN sys.foreign_key_columns AS fkc 
    ON fkc.parent_column_id = c.column_id
    AND fkc.parent_object_id = c.[object_id]
    WHERE fkc.constraint_object_id = fk.[object_id]
    ORDER BY fkc.constraint_column_id 
    FOR XML PATH(N''), TYPE).value(N'.[1]', N'nvarchar(max)'), 1, 1, N'')
  + ') REFERENCES ' + QUOTENAME(rs.name) + '.' + QUOTENAME(rt.name)
  + '(' + STUFF((SELECT ',' + QUOTENAME(c.name)
   -- get all the referenced columns
    FROM sys.columns AS c 
    INNER JOIN sys.foreign_key_columns AS fkc 
    ON fkc.referenced_column_id = c.column_id
    AND fkc.referenced_object_id = c.[object_id]
    WHERE fkc.constraint_object_id = fk.[object_id]
    ORDER BY fkc.constraint_column_id 
    FOR XML PATH(N''), TYPE).value(N'.[1]', N'nvarchar(max)'), 1, 1, N'') + ');'
FROM sys.foreign_keys AS fk
INNER JOIN sys.tables AS rt -- referenced table
  ON fk.referenced_object_id = rt.[object_id]
INNER JOIN sys.schemas AS rs 
  ON rt.[schema_id] = rs.[schema_id]
INNER JOIN sys.tables AS ct -- constraint table
  ON fk.parent_object_id = ct.[object_id]
INNER JOIN sys.schemas AS cs 
  ON ct.[schema_id] = cs.[schema_id]
WHERE rt.is_ms_shipped = 0 AND ct.is_ms_shipped = 0;

UPDATE #x SET create_script = @create;

PRINT @drop;
PRINT @create;

/*
EXEC sp_executesql @drop
-- clear out data etc. here
EXEC sp_executesql @create;
*/
Run Code Online (Sandbox Code Playgroud)

生成一堆:

ALTER TABLE [dbo].[Whatever] DROP CONSTRAINT....
--
ALTER TABLE [dbo].[Whatever] ADD CONSTRAINT....
Run Code Online (Sandbox Code Playgroud)

  • 糟糕的建议:"不要担心试图理解这个查询本身".如果不理解它,就不要把任何东西从网上运走 (16认同)
  • 了解查询的工作方式与确保查询不会造成任何伤害之间存在差异.后者几乎总是更容易. (4认同)
  • 简单地执行 TRUNCATE TABLE 就需要这种混乱的动态 SQL,这一事实令人反感。 (3认同)
  • 如上所述,这并没有使用"ON DELETE CASCADE"规则正确地重新创建约束.这是一个简单的修复,更改行'FOR XML PATH(N''),TYPE).value(N'.[1]',N'nvarchar(max)'),1,1,N'')+' );'``FOR XML PATH(N''),TYPE).value(N'.[1]',N'nvarchar(max)'),1,1,N'')+')ON DELETE '+ REPLACE(fk.delete_referential_action_desc,'_','')+';'` (2认同)
  • 请注意,“PRINT @drop”和“PRINT @create”语句将在 SQL Management Studio 中截断。如果您想要这些完整值,您将需要“SELECT * FROM #x”,然后从两个结果列中复制值。即便如此,我最终还是不得不`DECLARE @tempCreate NVARCHAR(MAX); 选择@tempCreate = create_script from #x; EXEC sp_executesql @tempCreate;` 用于我的创建语句。 (2认同)

Pau*_*oke 5

SQL服务器不允许您在约束存在时截断表,即使它已被禁用.删除约束并在截断表后重新创建约束.或者只需删除并重新创建表格,无论哪种更容易在您的应用程序中执行.

  • 你是什​​么意思不是交易命令?你可以把它回滚得很好.`CREATE TABLE Blah(一个int); INSERT Blah VALUES(1); SELECT*FROM Blah; BEGIN TRAN; TRUNCATE TABLE Blah; SELECT*FROM Blah; ROLLBACK TRAN SELECT*FROM Blah; DROP TABLE Blah`.Truncate通过释放整个页面而不是删除行来工作,但它仍然是事务性的. (2认同)
  • @Emtucifor,@pgroke,在某种程度上你们都是正确的,因为标准允许 TRUNCATE 是非事务性的,但允许实现使其成为事务性的。因此,TRUNCATE 的定义并不承诺可以完成回滚,但 SqlServer(和 Postgres)添加了超出标准的承诺。 (2认同)