fn_fixeddrives() : an alternative for xp_fixeddrives
The idea is to create a SQLCLR table valued function that returns all information on drives in a UNIX df-like style.
2010-09-21
9,832 reads
David Baffaleuf
Turn on CHECKSUM after an upgrade
When reloading or attaching a SQL 2000 database to SQL 2005 or 2008, the database objects are upgraded automatically. Some database options don't change, though. PAGE_VERIFY is one of them.
2010-07-20
7,199 reads
Blogs
Sample Data with GenAI in Seconds
By Steve Jones
A friend was asking for help with some data analysis. This was in PowerBI,...
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...
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...
do i lose what this object depends on etc when moving sprocs to etl server
Hi i was surprised to see the approach my coworkers used to sunset talend...
People Make Odd Choices
Comments posted to this topic are about the item People Make Odd Choices
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