Technical Article

Superior SQL Builder v1.3 released

Red Earth Technologies announces the release of version 1.3 of Superior SQL Builder, its SQL tool that allows users to visually build complete SQL scripts without typing any code.

Superior SQL Builder introduces new SQL scripting technology, allowing users to quickly and easily transform their database data. In version 1.3 this scripting technology has been extended and enhanced so that complex SQL scripts can be built in less time and with greater ease.

SQLServerCentral Article

Codd's Rules

Frank gives us his take on Codd's Rules. If you're new to databases, this is the core theory that resulted in the development of RDBMS. If you're more experienced with databases, maybe now is a good time to return to the rules to see how you're doing!

SQLServerCentral Article

Sequential Numbering

Needing to number rows with a sequential id is a pretty common request. Sometimes it's because the user hasn't made the transition to 'set based' thinking, sometimes it really is a valid request (more or less!). Greg provides several different techniques to help you achieve sequential numbering.

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