Check that what you expected is actually what you got - DB's and SQLCMD
I feel that it is wise move for a script to actually check itself that the database connection that is...
ShowPlan Operator of the Week - Merge Join
Did you ever wonder how and why your indexes affect the performances of joins? Once you've read Fabiano Amorim's unforgettable explanation, you'll learn to love the MERGE operator, and plan your indexes so as to allow the Query Optimiser to use it.
XQuery for the Non-Expert – @Variable Use
Talk to the Experts
In a previous post, I discussed the exist() method as part of the XQuery for the Non-Expert...
Skunk Works
The idea of a skunk works is to build a project that works under the radar, by a small and loosely organized group of people. Used to fuel innovation, this is an idea that you might apply to SQL Server BI projects.
Multi-subnet Failover Clusters
Multi-subnet Failover Clusters
I want to take a closer look at one of the new features in SQL Server Denali. While...
SQL Server Unit Testing with tSQLt
When one considers the amount of time and effort that Unit Testing consumes for the Database Developer, is surprising how few good SQL Server Test frameworks are around. tSQLt , which is open source and free to use, is one of the frameworks that provide a simple way to populate a table with test data as part of the unit test, and check the results with what should be expected. Sebastian Meine and Dennis Lloyd, who created tSQLt, explain
Why Every DBA Needs a Buddy
If you truly desire to be an effective SQL Server Database Administrator then you absolutely must have a buddy.
SQL Server...
Data Scientists
Would you want to be a data scientist? Are you one now? Steve Jones talks about this skill that we might appreciate in our daily work.
Making a more reliable and flexible sp_MSforeachdb
While the system procedure sp_MSforeachdb is neither documented nor officially supported, most SQL Server professionals have used it at one time or another. This is typically for ad hoc maintenance tasks, but many people (myself included) have used this type of looping activity in permanent routines. Sadly, I have discovered instances where, under heavy load and/or with a large number of databases, the procedure can actually skip multiple catalogs with no error or warning message. Since this situation is not easily reproducible, and since Microsoft typically has no interest in fixing unsupported objects, this may be happening in your environment right now
SQL University: Spring 2011
The new SQL University Logo
Welcome back students! We’re very excited to start up a new semester and SQLU is back and...
Blogs
T-SQL Tuesday #198 Roundup: How Do You Detect Data Changes?
Thank you to everyone who participated in T-SQL Tuesday #198! When I wrote the...
Optimizing Redshift Performance by Configuring WLM Queues
Efficient query performance in Amazon Redshift often comes down to how well you manage...
PowerShell Strikes Back: Return of the Loop
By gbargsley
Welcome back to PowerShell Strikes Back. We’re three weeks in, and the training is...
Forums
Stairway to Reliable Database Deployment Level 3 – Rehearsing Changesets Across Environments
Comments posted to this topic are about the item Stairway to Reliable Database Deployment...
QUOTENAME Quote Parameters
Comments posted to this topic are about the item QUOTENAME Quote Parameters
Limit the Blast Radius
Comments posted to this topic are about the item Limit the Blast Radius
Question of the Day
QUOTENAME Quote Parameters
When I use QUOTENAME(), I can optionally provide the character used to surround the string in the result. Can I use any character?
See possible answers