Tech on Tap v1.1 Wrap-up
The first ever Tech on Tap event was held on Saturday, January 27th, 2012 at the Stone Cellar Brewpub in...
2012-01-31
2,071 reads
The first ever Tech on Tap event was held on Saturday, January 27th, 2012 at the Stone Cellar Brewpub in...
2012-01-31
2,071 reads
The question came up, what are the top 3-5 things that you look at in a query. I realized then...
2012-01-30
1,827 reads
There are four different ways you can get information about deadlocks in your system. These are:
traceflag 1204traceflag 1222trace eventsextended eventsFor...
2012-01-27 (first published: 2012-01-23)
3,082 reads
I’m not going to black out my blog, because, let’s face it, who’s going to notice? But for all six...
2012-01-18
1,920 reads
I want to say a few things about database backups that you need to know.
Wait a minute, haven’t you written...
2012-01-16 (first published: 2012-01-11)
5,164 reads
Gee thanks Jes (blog|twitter). Just what I wanted, a little extra work on a Friday afternoon. I used to like...
2012-01-13
1,435 reads
I say it all the time because it’s worth repeating, feedback is a gift. Good, bad or indifferent (well, not...
2011-12-19
1,730 reads
I’ll be presenting at the Colorado Springs SQL Saturday on January 7th of 2012. The session is called Seven Ways...
2011-12-14
1,932 reads
I’ve been working with execution plans quite a lot in SQL Server 2012. There are a number of changes, most of them associated with new or different functionality. I had not noticed anything really fundamental until recently. I’ve become a huge proponent of always checking the properties of the SELECT statement. There’s so much useful information in there about what’s happened with the plan generation in the optimizer (not low level stuff, but the big picture items) that you should always be checking it first as a fundamental part of your plan examinations.
2011-12-14
6,689 reads
I’ve been working with execution plans quite a lot in SQL Server 2012. There are a number of changes, most...
2011-12-12
10,169 reads
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
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...
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