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 Vinay Thakur
Continued thinking about my Journey blog where we have to look back at the...
By James Serra
A ton of new features for Microsoft Fabric were announced at the Microsoft Fabric Community...
By SQLPals
PowerShell Remoting for SQL DBAs: WinRM + SSH Guide (Updated 2026) ...
Comments posted to this topic are about the item Identities and Sequences II
Comments posted to this topic are about the item Using PostgreSQL as a NoSQL...
Comments posted to this topic are about the item Is Your Time "Free"?
In thinking about the differences between the identity property and a sequence object, which of these two guarantees that there are consecutive numbers (according to the increment) inserted in a single table?
See possible answers