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

Why your data still can’t answer a simple question 

By

Every organization I talk to has the same problem dressed up in different clothes....

T-SQL Tuesday #197 Invitation – An impactful session or two from a conference

By

I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...

Did You Really Name That Default?

By

Ten years (and a couple jobs) ago, I wrote about naming default constraints to...

Read the latest Blogs

Forums

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

By Terry Jago

Comments posted to this topic are about the item The day-to-day pressures of a...

The Problem Isn't Always Your Query or Schema... Sometimes It's Hidden Assumptions

By dbruton95

Comments posted to this topic are about the item The Problem Isn't Always Your...

Identity Defaults

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Identity Defaults

Visit the forum

Question of the Day

Identity Defaults

What happens when I run this code?

CREATE TABLE dbo.IdentityTest
(
     id int IDENTITY(10) PRIMARY KEY,
     somevalue VARCHAR(20)
)
GO

See possible answers