SQLServerCentral Article

SQL Backup 3.0

SQL Server 2000 has a rock solid backup process and one that many people have relied upon for years. However with the growth in database sizes and the constant load on many database servers, a third party backup utility is almost required in many environments. Kathi Kellenberger takes a look at Red-Gate Software's SQL Backup 3.0 and how it performs in her environment.

Technical Article

The Advent of E3

A few months ago we ran a series of columns dedicated to defining each of the major disciplines of data integration: extract, transformation and load (ETL); enterprise application interchange (EAI); and enterprise information integration (EII). We also asked for input as to which method or methods of integration are in use, or planned to be used, in your organizations.

SQLServerCentral Article

Inside SQL Server Development

After the announcement last week by Microsoft that there would be no Beta 3 for SQL Server 2005 and that the CTP process would take over, Steve Jones had the opportunity to interview Thomas Rizzo and Allan Ros from the SQL Server development team about the CTP process and testing the SQL Server builds.

External Article

Formatted emails from SQL Server

Collaboration Data Objects, also called CDO, is designed to simplify writing programs that create or manipulate Internet messages. CDO for Windows 2000 is an integral part of the Windows 2000 and higher series of operating systems. It is easy to send SMTP email from SQL Server using CDOsys. It is an alternate method to SQLMail. This article illustrates how to use CDOSys to send formatted emails from Query Analyzer and SQL Server Alerts.

Technical Article

Managing the "Surface Area" of SQL Server 2005

As every developer knows by now, Microsoft has focused renewed attention on security in recent product releases. One of the important concepts in this effort is surface area. Roughly speaking, a piece of software has a smaller surface area if there are fewer ways to attack it: fewer open ports, fewer APIs, fewer protocols, and so on. OSQL Server 2005 takes this concept to the next level by letting you explicitly manage the software's surface area.

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