External Article

When SQL Server Performance Goes Bad: Implicit Conversions

When you're developing a database, the pressure is on to get something that works, using an efficient algorithm. When you are getting close to a release candidate, however, there are some programming habits that must be removed from the code, because they can cause unexpected performance problems. In this article, you'll learn how to detect and remove one such problem: reliance on implicit datatype conversions in your queries. We'll use a combination of plan cache queries, extended events, and SQL Monitor.

SQLServerCentral Editorial

Do You Have Big Data?

Data sizes are always growing. Stats on world data are astounding, as are the stats many of us experience in our lives. Plenty of us have moved from MB management to GBs, and I see plenty of people dealing with TB storage at home. Most of that data is likely from images and video, but […]

Blogs

Learn about Modern Microsoft Apps in San Diego

By

I wrote about learning today for the editorial: I Can’t Make You Learn. I...

How To Deploy Fabric SQL and Azure SQL Databases with Azure DevOps

By

Fabric has CI/CD built in, but if you've tried to use it for database...

A New Word: Attriage

By

attriage – n. the state of having lost all control over how you feel...

Read the latest Blogs

Forums

Forward Deployed Engineers

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Forward Deployed Engineers

TRY_PARSE vs TRY_CONVERT in SQL Server: From Basics to Practical Usage

By john.martin

Comments posted to this topic are about the item TRY_PARSE vs TRY_CONVERT in SQL...

DBCC CHECKDB Limits II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKDB Limits II

Visit the forum

Question of the Day

DBCC CHECKDB Limits II

I have a SQL Server 2025 database that I want to check for corruption every night. One of the things we do is disable indexes used for ETL loads during the weekend and re-enable them on Monday morning. If we run DBCC over the weekend, are our disabled indexes checked for consistency?

See possible answers