One size does not fill all
Allowing your application to generate your SQL can be a really bad decision.
2014-03-06
195 reads
Allowing your application to generate your SQL can be a really bad decision.
2014-03-06
195 reads
Today we have a guest editorial from Jim Youmans that asks "what does it mean to be a DBA today?"
2013-12-06
406 reads
2013-11-25 (first published: 2013-11-15)
2,194 reads
Create restore script from a SQL Backup file. A must have for your DBA Tool Belt.
2013-06-18 (first published: 2013-05-30)
2,308 reads
Need to find every stored procedure in any database that references the table FooBar? Here is a quick and easy search to do that.
2013-05-30 (first published: 2013-05-22)
1,724 reads
2013-04-30
690 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