2023-10-20
453 reads
Truncate Table
2023-10-16
505 reads
Truncate a table that has foreign keys referencing its columns
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)
844 reads
Grant Truncate Table Permissions in SQL Server without ALTER Table
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,785 reads
2014-09-29 (first published: 2010-02-04)
9,468 reads
usp_ShrinkAllLogs
Replacement script for usp_ShrinkDBLogs, updates for SQL 2008 deprecating the WITH TRUNCATE_ONLY method.
2009-11-27 (first published: 2009-10-30)
973 reads
2011-06-03 (first published: 2008-08-18)
1,080 reads
Blogs
Time to Revive our YouTube Channel
It’s been forgotten about and neglected for few years but I’ve decided to dust...
Microsoft MVP 2025: Continuing the Data Platform Journey
I am honored to announce that I have been renewed as a Microsoft MVP...
What is KTLO? Keep The Lights On vs Project Work in Agile
By Rohit Garg
🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
Forums
How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory
Comments posted to this topic are about the item How a Legacy Logic Choked...
Import/Export SSMS Settings issue
I have tried a number of times to export and then import my SSMS...
FQDN - SQL cannot connect when the server name has backslash
Hi I need to connect to a SQL server via FQDN - that is...
Question of the Day
Query Plan Regressions --
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers