Detective Stories - Tracking Down the Database's Dependents Part 2
No worries about dropping databases. Now we can search for its dependencies before the database dies. Part 2 of a 2-part article.
No worries about dropping databases. Now we can search for its dependencies before the database dies. Part 2 of a 2-part article.
Once you have Query Store enabled on your databases, runtime statistics are generated for your queries; but what about the natively-compiled stored procedures and memory optimised tables that come with In-Memory OLTP? Do you get the full range of runtime statistics? This is an intriguing question that Enrico explores and answers.
Join the SSIS Catalog Compare v2.0 Launch Event on Tue, Mar 7 at 13:00 EST.
Containers are valuable in many software domains. Are there places we, as data professionals, would like to use software containment?
If a successful IT career is just as much about tenacity, interest and retention as it is about brainpower, then how does one go about continuous learning?
No worries about dropping databases. Now we can search for its dependencies before the database dies. Part 1 of a 2-part article.
The SQL Server Luxembourg User Group invites you to join us at our next event in Microsoft’s Offices, at 6:00pm on Tuesday 7th March
Greg Larsen explains how you can use Dynamic Management Objects and stored procedures to return your worst performing T-SQL statements.
An open letter to Microsoft from the CEO of Mandriva Linux might not have been the best idea.
Today Steve Jones asks what default values you might choose for new columns in a table.
Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...
By Steve Jones
I don’t have SQL Server installed on my laptop. In an effort to keep...
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