Database Superhero Adventures, February 2018 Edition
vs.
The week of SQLSaturday Nashville would prove to be a most eventful week. Monday I would be on my work...
2018-02-01
123 reads
vs.
The week of SQLSaturday Nashville would prove to be a most eventful week. Monday I would be on my work...
2018-02-01
123 reads
Earlier this week the folks at PASS reached out to last year’s speakers asking us to share a story of...
2018-01-27
132 reads
This is part 2 of 2 on taking smart backups. I wrote a previous blog on how to use configuration...
2018-01-23
136 reads
This T-SQL Tuesday is brought to us by Arun Sirpal (b | t) and wants to write about a technical challenge...
2018-01-09
135 reads
This is part 1 of 2 part series on taking smart backups. Part 1 will be taking smart transaction logs...
2018-01-02
179 reads
Just in case you missed it I wrote a blog post for Idera on creating PowerShell module using Plaster you...
2018-01-01
124 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