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
The First Steps: Understanding the Basics of FinOps
By HeyMo0sh
As a DevOps professional, I’ve seen firsthand how cloud costs can quickly spiral out...
Monday Monitor Tips: AI Query Analysis
By Steve Jones
AI is everywhere. It’s in the news, it’s being added to every product, management...
AI: Blog a Day – Day 8: RAG – Retrieval Augmented Generation
By Vinay Thakur
RAG — Retrieval Augmented Generation. we have covered so far — embeddings, vectors, vector...
Forums
would it be so terrible to install ssms on a few user desktops?
Hi, ssms is free here. I can think of other reasons to do this...
I'm thinking about submitting some articles
I've written some documentation on using different Markdown types of files on GitHub. It's...
Not Just an Upgrade
Comments posted to this topic are about the item Not Just an Upgrade
Question of the Day
Restoring On Top I
I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?
USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO USE DNRTest GO CREATE TABLE MyTest(myid INT) GO USE master RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACESee possible answers