After the crash of an US Air Force database was reported, Steve Jones has some advice.
We are excited to announce the beta release of SQL Compare & SQL Data Compare 12. We want to use this beta period to get as much feedback from you, the SQL community, as possible. Try it out, or for more information on what’s new, read on.
Jonathan Kehayias takes a closer look at a new trace flag that allows you to process multiple concurrent statistics updates on the same table.
SQL Server 2016 runs faster, sometimes without you changing anything.
This article presents a utility that will show you what SQL statements are using the transaction logs, in terms of log space used and transaction duration.
In SQL Server Master Data Services all the entities are organized in a model. Once a model is ready to be released to subscribers, it should be frozen and marked as ready for subscribers. Until a model is marked as ready, a model is typically deemed as work in progress. In this article, Siddarth Mehta covers the standard process that's required to release a completed version of the model to subscribers.
Knut Jürgensen shares his experiences, both positive and negative, with regard to the function that Master Data Management fulfils within a company. Too often this critical aspect of a business is overlooked or pushed aside without paying it the attention it deserves based on the cost benefits available.
The Stretch database feature in SQL Server 2016 is fantastic, but is it too expensive?
By Brian Kelley
My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...
By Steve Jones
“On the way to a grand goal, celebrate the smallest victories as if each...
Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...
Comments posted to this topic are about the item Increase Deadlock Detection
Comments posted to this topic are about the item A Tool is Better than...
Comments posted to this topic are about the item Understanding Deadlock Victim Selection in...
How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?
See possible answers