How to Move System Databases to a New Physical Directory
What is the easiest way to move SQL Server system databases. Let me walk you through it!
2020-05-25
27,632 reads
Databases
2014-06-11
1,854 reads
2011-12-08
2,257 reads
2014-09-23 (first published: 2010-02-17)
11,452 reads
2009-04-28
2,363 reads
Growth remaining for SQL Server 2005 databases
This script is little bit similar to the one posted for SQL Server 2000 that finds how much space you have left.
2009-01-30 (first published: 2009-01-19)
939 reads
Blogs
TSQL Tuesday #188 Growing community
I am responding late to a T-SQL Tuesday invite from John Sterrett. John’s call...
Time to Revive our YouTube Channel
It’s been forgotten about and neglected for few years but I’ve decided to dust...
Microsoft MVP 2025: Continuing the Data Platform Journey
I am honored to announce that I have been renewed as a Microsoft MVP...
Forums
How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory
Comments posted to this topic are about the item How a Legacy Logic Choked...
People Make Odd Choices
Comments posted to this topic are about the item People Make Odd Choices
SQL Server 2022 Clusterless Distributed Availability Group
Comments posted to this topic are about the item SQL Server 2022 Clusterless Distributed...
Question of the Day
Query Plan Regressions --
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers