How to make Net Meeting a success
This article is a basic guide line to chapter leaders who are planning to have Net meetings as part of the User Group meetings.
2011-01-20
1,076 reads
Articles
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...
2011-01-20
1,930 reads
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.
2011-01-20
3,194 reads
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...
2011-01-20
2,997 reads
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...
2011-01-19
2,819 reads
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
2011-01-19
3,084 reads
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...
2011-01-19
2,790 reads
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
2011-01-18
3,580 reads
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...
2011-01-18
1,258 reads
31 Days of SSIS – Create XML Document (13/31)
31 Days of SSIS
Day thirteen and we are trucking along with the 31 Days of SSIS blog series. The last...
2011-01-17
2,056 reads
Blogs
Deployment Pipelines in Fabric – What Are They?
By HeyMo0sh
In the realm of software development and content creation, the deployment pipeline serves as...
TempDB Internals – What’s New (SQL Server 2016 to 2022)
By Vinay Thakur
I wrote about TempDB Internals and understand that Tempdb plays very important role on...
Forums
A Quick Restore
Comments posted to this topic are about the item A Quick Restore
Guarding Against SQL Injection at the Database Layer (SQL Server)
Comments posted to this topic are about the item Guarding Against SQL Injection at...
Ola Hallengren Index Optimize Maintenance can we have data compression = page
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
Question of the Day
A Quick Restore
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers