Additional Articles


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.

2020-07-29

Blogs

Monday Monitor Tip: Compliance Checking for Old Versions

By

A customer recently wanted to know if any of their instances were too old...

Making Legend Order Match Segment Order in a Power BI Stacked Column Chart

By

A reader of one of my previous posts pointed out that the legend order...

The Only Valid Test of a Backup is a Restore

By

Please, let me reiterate: The only valid test of a backup is a restore....

Read the latest Blogs

Forums

sql service account

By mtz676

We are trying to update a sqlservice account from a user account to a...

Help with index rebuild

By dnison-905607

Hi there!  This should make some eyes roll for some of you DBA's out...

Cannot connect to Analysis Services via Excel

By Bhagat

For myself this seems to work and for other users they receive this error:...

Visit the forum

Question of the Day

Migration Assistant Issues

If I run the Data Migration Assistant to check for an upgrade from SQL Server 2008 to SQL Server 2022, which categories of issues are pointed out as potential items that can affect an upgrade? (choose 3)

See possible answers