SQLServerCentral Editorial

The Disappearing DBA

During a "difficult period", a developer often sinks from view. When things are going well, suddenly they are the gunslinger, the hotshot. The DBA often looks on wistfully. For him, the "fame trajectory" seems to work in reverse.

Technical Article

Handling workloads on SQL Server 2008 with Resource Governor

SQL Server 2005 resource allocation policies treat all workloads equally, and allocate shared resources as they are requested. It sometimes causes a disproportionate distribution of resources, which in turn results in uneven performance or unexpected slowdowns whereas the new Resource Governor of SQL Server 2008 allows organizations to define resource limits and priorities for different workloads, which enables concurrent workloads to provide consistent performance to the end users.

Technical Article

LinkedIn - Part 2

Recently I posted LinkedIn (part 1) about my efforts to better understand and use it as a networking platform. It ended up generating a lot of good comments, always nice to see, and I'll be addressing some of those here and/or in part 3 coming up...

Blogs

T-SQL Tuesday #202 Invitation: That One SQL Server Outage You’ll Never Forget

By

I am excited to host T-SQL Tuesday for the first time. I want to...

A Daily Report from Claude

By

Redgate had some Claude training recently, which I went through as my knowledge has...

A New Word: Gnossienne

By

gnossienne– n. the awareness that someone you’ve known for years still has a private...

Read the latest Blogs

Forums

Measuring Productivity

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Measuring Productivity

Importing Excel files into SQL Server using DuckDB and Python

By Cláudio Tereso

Comments posted to this topic are about the item Importing Excel files into SQL...

Tracking All the Queries

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Tracking All the Queries

Visit the forum

Question of the Day

Tracking All the Queries

I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?

See possible answers