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.
Learn how you can use Polybase technology in Azure Synapse to load data into your warehouse.
Phil Factor dissects and disentangles the various SQL Compare options.
In this article we look at different T-SQL code examples that can help you build a range of date rows based on a starting and ending date.
A failed SQL Server Service Pack upgrade is fixed with a trace flag.
Steve reflects on some of the ideas of how Microsoft imagines the future of computing.
In this article we cover many different questions about the SQL Server TempDB database to give a better understanding of what is and what it is used for.
By gbargsley
Do you run SQL Agent Jobs in your environment? Do you know what is...
By Steve Jones
When I got a new machine, I had SQL Clone on my old machine,...
By Steve Jones
I started to add a daily coping tip to the SQLServerCentral newsletter and to...
I have set up an extended event to capture the queries users may be...
Okay, maybe I've just gone crazy but I was certain it used to be...
Hello, I have a recursive Select that runs ultra slow. My test table has...
Ask SSC