2015-12-21
325 reads
2015-12-21
325 reads
Louis Davidson explains why a little database courtesy goes a long way.
2015-11-16
230 reads
Whose fault is it if a database is hacked and its contents appear on a hacker’s site? Louis Davidson suggests that, regardless of limitations, the DBA always bears some responsibility.
2014-12-22
161 reads
2014-11-24
167 reads
In opera, tragedy or absurdity happens because the characters are incapable of standing back, and making a difficult decision. Instead, at every stage, they just drift towards their fate by taking the easy option. Don't let the same fate befall you, as a DBA.
2014-08-04
117 reads
Louis Davidson on why DBAs ought to do one thing, every day, that is scary.
2014-07-07
224 reads
As a professional, our knowledge of a given task should extend, at a minimum, one level deeper than is strictly necessary to perform the task. Anything deeper can be left to the ridiculously smart, or obsessive, or both
2014-05-12
122 reads
Louis Davidson on the small dreams that DBAs can nurture, each day, to elevate the drudgery of a seemingly banal task into a celebration of purpose.
2014-03-03
166 reads
Like Sherlock Holmes, a DBA needs the sound deductive reasoning to pinpoint the root cause of a crime, in amongst a thousand interesting but irrelevant details.
2013-11-18
139 reads
Technical debt is frustrating but dealing with it requires patience. Louis Davidson explains why.
2013-09-02
142 reads
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
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...
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