SQLServerCentral Article

An Introduction to the Service Broker

One of the more interesting new features in SQL Server 2005 is the Service Broker. It's not something to help you manage your financial future, nor is it some new program that handles all the instances and their accounts. It's a message queue and SQL Server MVP Srinivas Sampath brings us a look at this new feature with some code to get you going.

SQLServerCentral Article

Exception handling in DTS

While SSIS is taking the SQL Server 2005 world by storm, there are many DBAs still working with SQL Server 2000 and its ETL system: DTS. In this article, Jambu Krishnamurthy shows us how to modify the exception handling in a DTS package to get around the limitations of the designer.

Technical Article

Log Shipping with SQL Server 2005

Log shipping has been a mechanism for maintaining a warm standby server for years. Though SQL Server supported log shipping with SQL Server 2000 as a part of DB Maintenance Plan, it has become a built-in feature of SQL Server 2005. This article gives brief introduction to SQL Server 2005 Log Shipping, configuration of it, monitoring of it and failing over at the disaster.

Blogs

From Planning to Practice: Setting Up Your FinOps Framework

By

As someone who works in DevOps, I’m always focused on creating systems that are...

“We love to debate minutiae”

By

I am guilty as charged. The quote was in reference to how people argue...

Advice I Like: Knots

By

Learn how to tie a bowline knot. Practice in the dark. With one hand....

Read the latest Blogs

Forums

Restoring On Top II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Restoring On Top II

SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)

By Terry Jago

Comments posted to this topic are about the item SQL Art 2: St Patrick’s...

Breaking Down Your Work

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Breaking Down Your Work

Visit the forum

Question of the Day

Restoring On Top II

I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:

-- run yesterday
CREATE DATABASE DNRTest2
GO
USE DNRTest2
GO
CREATE TABLE NewTable (id INT)
GO
Today, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today
USE Master
BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens?

See possible answers