External Article

Best Practice for renaming a SQL Server Database

One of the Junior SQL Server Database Administrator in my company approached me yesterday with a dilemma. He was assigned a task to rename few of the databases in Beta and Production environments; the reason being the database name was based on some other project that is no longer relevant to the data which is presently stored within the database. At first I started to tell him, but figured it would be smarter to document the same and share the information.

Technical Article

Life Logging

Would you like the idea of capturing everything you do? Audio, video, text, code, a log of your life. A new book from Microsoft Research talks about this and Steve Jones things it could be an interesting capability for your career.

Blogs

SWAG Saves the Day

By

PASS Summit East is in one week. I was on the road last week...

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

How to Find Expensive Queries in Amazon Redshift

By

Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...

Read the latest Blogs

Forums

Having Issue deploying a report to an on prem server from PowerBI desktop

By daniel.manke

Using PowerBI Version1.25.9508.3237(January 2026). Installed Microsoft Power BI Desktop (Optimized for Power BI Report...

SQL 2019 instance with AG, across 2 Windows 2016 OS servers - OSin-place upgrade

By millardus

Hi all Can I get some perspective from the community please on performing in-place...

How Long is a Long I/O?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item How Long is a Long...

Visit the forum

Question of the Day

How Long is a Long I/O?

In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?

See possible answers