Truncate tables where Referential Integrity exists
This script can be useful in test and dev environments to quickly clear tables via the truncate command where referential integrity exists.
2024-05-15 (first published: 2024-05-02)
861 reads
This script can be useful in test and dev environments to quickly clear tables via the truncate command where referential integrity exists.
2024-05-15 (first published: 2024-05-02)
861 reads
2023-10-16
559 reads
A new error message in SQL Server 2019 will make your life much easier!? Learn more...
2019-03-05
3,244 reads
Truncating tables with constraints always had been a pain, since we have to drop and recreate all the FKs. I created a script that takes care of dropping and recreating the foreign keys while truncating. Please use with caution! and always respect your Data !
2016-12-01 (first published: 2016-11-28)
1,422 reads
2014-09-11
2,394 reads
This article describes a way to identify the user who truncated the table & how you can recover the data.
2015-02-20 (first published: 2014-06-05)
34,868 reads
By Steve Jones
semaphorism – n. a conversational hint that you have something personal to say on...
This week I was at PASS Data Community Summit in Seattle, and I attended...
By James Serra
(This is the third post in a three-part series on how AI is changing...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Helping an English Student with...
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, 'true')
GO
See possible answers