External Article

SQL Server Data Type Precedence

I am executing a simple query/stored procedure from my application against a large table and it's taking a long time to execute. The column I'm using in my WHERE clause is indexed and it's very selective. The search column is not wrapped in a function so that's not the issue. What could be going wrong?

SQLServerCentral Article

The Ego, the Id and the DBA

In most organizations, the DBA team is seriously outnumbered by headstrong developers and clock driven managers, and "great" DBAs will often be outnumbered by...well...the not so great. In order to be heard in this environment, a DBA will not only need to be very skilled, but will also need a healthy dose of ego.

Blogs

In-Person CISA Training – April 13-16, 2026

By

I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...

EightKB 2026

By

EightKB is back again for 2026! The biggest online SQL Server internals conference is...

The FinOps Lifecycle: From Budgeting to Reporting

By

Working in DevOps long enough teaches you two universal truths: That’s exactly why I...

Read the latest Blogs

Forums

query to track time spent on individual tasks in SSIS

By water490

Hi everyone I am looking at building a query to determine how much time...

SQL Server Transactional Replication from Always On Availability Groups to Azure SQL Database

By Terry Jago

Comments posted to this topic are about the item SQL Server Transactional Replication from...

Hidden Heroes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Hidden Heroes

Visit the forum

Question of the Day

Identities and Sequences I

When thinking of the Identity property for auto incrementing columns and sequences for the same action, which are explicitly linked to increment a number in a table when a new row is added?

See possible answers