External Article

What does SET NOCOUNT ON do?

When you’re working with T-SQL, you’ll often see SET NOCOUNT ON at the beginning of stored procedures and triggers. What SET NCOUNT ON does is prevent the “1 row affected” messages from being returned for every operation. Read Brent's blog to see him demo it by writing a stored procedure in the Stack Overflow database.

SQLServerCentral Editorial

Happy Birthday USA!

This is the Fourth of July weekend here in the US when we celebrate the birth of the country based on the publication of the Declaration of Independence. For those who don't know, this celebration mostly consists of fireworks and outdoor cookouts. However, at our house we've always tried to do a little bit more […]

SQLServerCentral Editorial

Learning Intentionally with a List

We're coming up on the middle of the year, and I wonder if you are improving your career this year? Did you make plans and are you sticking to them? I've been tracking progress on my goals, and so far mediocre progress. It's tough to learn, but even tougher to learn when you don't have […]

Blogs

Whiling away an afternoon, thinking

By

I come to Heathrow often. Today is likely somewhere close to 60 trips to...

Black Box vs. Gray Box vs. White Box Testing

By

If your organization is spending money, then meaningful results are a must. Pen testing...

Webinar Series – SQL Server Indexing

By

I’m starting a webinar series about SQL Server indexing with the fine folks of...

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