External Article

What If You Really DO Need to Shrink a Database?

You’ve heard that shrinking a database is bad because it introduces both external and internal fragmentation, it causes blocking, it causes transaction log growth while it runs, and it’s slow and single-threaded. You understand that if it’s just a matter of 10-20-30% of a database, and the database is only 100-200GB, you might as well just leave the space there, because you’re gonna end up using it anyway.

Blogs

Modify Power BI page visibility and active status with Semantic Link Labs

By

Setting page visibility and the active page are often overlooked last steps when publishing...

T-SQL Tuesday #190–Mastering a New Technical Skill

By

It’s time for T-SQL Tuesday again and this time Todd Kleinhans has a great...

Getting Started with the MSSQL AI Agent in VS Code

By

Recently I was working in VS Code and I saw a walkthrough for the...

Read the latest Blogs

Forums

Azure elastic query credential question

By cphite

I am trying to check out elastic query between two test instances we have...

Change Tracking Data Retention Options

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Change Tracking Data Retention Options

Requiring Technical Debt Payments

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Requiring Technical Debt Payments

Visit the forum

Question of the Day

Change Tracking Data Retention Options

If I am running this code:

ALTER DATABASE AdventureWorks2017 SET CHANGE_TRACKING = ON (CHANGE_RETENTION=4 xxx);
What are the possible choices for xxx?

See possible answers