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
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
Forums
Windows logins for users migrated from DomainA to DomainB
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Multiple Deployment Processes
Comments posted to this topic are about the item Multiple Deployment Processes
How to Use sqlpackage to Detect Schema Drift Between Azure SQL Databases
Comments posted to this topic are about the item How to Use sqlpackage to...
Question of the Day
Upgrading Admin Queries
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers