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 Steve Jones
The greatest rewards come from working on something that nobody has words for. If...
By HeyMo0sh
Working in DevOps, I’ve seen FinOps do amazing things for cloud cost control, but...
Every organization I talk to has the same problem dressed up in different clothes....
Comments posted to this topic are about the item The day-to-day pressures of a...
Comments posted to this topic are about the item Creating a Simple and Flexible...
When thinking about the identity property and sequence objects, which of these can be used with numeric and decimal data types?
See possible answers