2015-01-23 (first published: 2013-10-08)
29,989 reads
2015-01-23 (first published: 2013-10-08)
29,989 reads
Ever need to automatically stop a long running job? Ever need to find which named Schedule is the currently running version of your job? There's simple code that'll let you find out.
2013-04-25
6,139 reads
In part II of this series, Sioban Krzywicki shows us another way Tally Tables have helped solve problems - Text Parsing.
2010-08-03
9,420 reads
In the first part of a series on Tally Tables, Sioban Krzywicki shows how a Tally Table has helped out with fiscal year calculations.
2010-08-02
16,486 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
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) GOToday, 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 REPLACEWhat happens? See possible answers