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

Changing the Cardinality of a FK in Redgate Data Modeler

By

One of the things a customer asked recently about Redgate Data Modeler was how...

Future-Proofing: How to Stay Ahead in FinOps

By

Cloud environments don’t sit still. Pricing models change, services evolve, workloads grow, and suddenly...

Introducing the SQL Server on Kubernetes Operator

By

Are you considering replatforming your SQL Server workload due to recent vendor changes, but...

Read the latest Blogs

Forums

Removing TDE

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Removing TDE

Poor Names

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Poor Names

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

By Terry Jago

Comments posted to this topic are about the item The day-to-day pressures of a...

Visit the forum

Question of the Day

Removing TDE

How do I remove TDE encryption of data from database xxx?

See possible answers