Truncate Table Pitfalls

 Truncate Table Pitfalls
Truncating a table can be gloriously fast—and spectacularly dangerous when used carelessly. If you want the speed without the face-palm moments, here’s a practical, interview-ready guide to...

2025-10-29 (first published: )

1,021 reads

Blogs

Using AI to Build Semantic Models, Ontologies, and Fabric Data Agents

By

(This is the third post in a three-part series on how AI is changing...

SSMS Is Getting Smarter—and This Isn’t Just About Writing SQL

By

Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...

Yippee-Kai-Yay 2027 Summit in Denver

By

Next year the PASS Data Community Summit is in DENVER! and London, but Denver...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

Life hack that has worked well for me

By skeleton567

I wrote about this several years ago but will contribute again a life hack...

Trying to make this faster using not exists

By krypto69

Hi I have this query that is slow during the 'not in' part of...

Visit the forum

Question of the Day

Switching Schemas I

I run this query: 

SELECT 
 s.name AS schemaname
 , o.name AS objectname
 FROM sys.objects o
 INNER JOIN sys.schemas s ON s.schema_id = o.schema_id
 WHERE o.name = 'Beer'
I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code: 
ALTER TABLE dbo.beer switch TO etl.beer
What happens?

See possible answers