2023-10-20
462 reads
2023-10-20
462 reads
2023-10-16
511 reads
This stored procedure will truncate a table even when other tables have FKs referencing columns in it. It drops the Fks, truncates the table, re-creates the FKs
2017-04-19 (first published: 2017-03-28)
857 reads
How do you grant a SQL Server developer truncate table permission without giving them the ability to alter the table? Check out the examples and explanation in this tip.
2012-01-16
3,333 reads
2010-02-05
4,799 reads
2014-09-29 (first published: 2010-02-04)
9,474 reads
Replacement script for usp_ShrinkDBLogs, updates for SQL 2008 deprecating the WITH TRUNCATE_ONLY method.
2009-11-27 (first published: 2009-10-30)
978 reads
2011-06-03 (first published: 2008-08-18)
1,082 reads
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers