TSQL Tuesday #2
I’ve wracked my brain for some bit of puzzle that I could present as part of TSQL Tuesday #2 and I...
2010-01-12
1,121 reads
Grant Fritchey
- Twitter: @https://twitter.com/gfritchey
- Website: https://scarydba.com
- LinkedIn: https://www.linkedin.com/in/grant-fritchey/
- Bluesky: https://bsky.app/profile/gfritchey.bsky.social
Horror… sort of
You must read this post from Tim Ford to understand why I might do this on my technical blog. But...
2010-01-11
883 reads
New England Data Camp v2/SQL Saturdy #34 Update
The second annual New England Data Camp is shaping up to one excellent event. We’ve put together a great set...
2010-01-11
550 reads
PASS Summit Evaluations
The big day has arrived and all the speakers are poring over their PASS Summit 2009 evaluations, me included. These...
2010-01-06
694 reads
Be Prepared
Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.
2010-01-04
376 reads
SQL Server Standard Article Abstracts
I’d really like to publish your article in SQL Server Standard. All I need from you is an abstract, a...
2010-01-04
959 reads
Be Prepared
Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.
2010-01-04
2,109 reads
Be Prepared
Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.
2010-01-04
2,707 reads
Be Prepared
Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.
2010-01-04
2,236 reads
Plagiarism
And really bad plagiarism at that.
I received an email from someone suggesting I check out a book on Lulu.com, that...
2010-01-01
1,029 reads
Blogs
Tooling for Success: The Best FinOps Tools and Technologies
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
From Planning to Practice: Setting Up Your FinOps Framework
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Forums
Restoring On Top II
Comments posted to this topic are about the item Restoring On Top II
SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Breaking Down Your Work
Comments posted to this topic are about the item Breaking Down Your Work
Question of the Day
Restoring On Top II
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