Risk and Assumptions
Building software always involves risk, but in these tough times, Steve Jones thinks we should be working to lower the risk of IT projects.
2013-09-13 (first published: 2009-01-22)
214 reads
Building software always involves risk, but in these tough times, Steve Jones thinks we should be working to lower the risk of IT projects.
2013-09-13 (first published: 2009-01-22)
214 reads
Dealing with a disaster is a trying experience for anyone, but having to then worry about having the proper software installed can make things much worse. Steve Jones talks a bit about the challenges of worrying about software versions.
2013-09-12 (first published: 2008-12-17)
342 reads
2013-09-12
2,077 reads
I wrote a post about creating a Filetable, which just covered the basics of how to build one. How do...
2013-09-11
1,087 reads
In part 3 of his thoughts on certifications, Steve Jones gives an idea for how we might move forward from here.
2013-09-11
142 reads
2013-09-11
2,475 reads
It’s T-SQL Tuesday time again. This is the monthly blog party where we all write on a topic. This month...
2013-09-10
1,013 reads
Part 2 of a set of thoughts from Steve Jones on certification in technology areas.
2013-09-10
378 reads
With the discontinuing of the MCM And MCA programs, Steve Jones has a few thoughts. This is the first of a three part series on certifications.
2013-09-09
244 reads
The news about NSA spying keeps coming out, and apparently includes corporate communications as well.
2013-09-09
287 reads
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
I’m starting a webinar series about SQL Server indexing with the fine folks of...
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