External Article

SQL# (SQLsharp): A Review

Only the brave, and foolhardy, write production CLR routines if you can get the functionality already-written and tested. Whether you’re a DBA or developer, there are plenty of times when a CLR routine will save a lot of time, and occasionally provide new functionality.

External Article

Auditing DDL Changes in SQL Server databases

Even where Source Control isn't being used by developers, it is still possible to automate the process of tracking the changes being made to a database and put those into Source Control, in order to track what changed and when. You can even get an email alert when it happens. With suitable scripting, you can even do it if you don't have direct access to the live database. Grant shows how easy this is with SQL Compare.

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