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

Ramblings about data communities and your contributions, no excuses

By

I have been active in the data community throughout my career. I have met...

SQL Server Journey till 2025 (brief)

By

Quick Summary for Microsoft SQL Server till 2025, I am fortunate to be part...

Building Power BI Reports: Desktop vs Fabric

By

Why this comparison feels confusing If you’re a Power BI report author who’s just...

Read the latest Blogs

Forums

Multi-State Payroll Tax Issues 2026

By davidholland0703

Prepare for 2026 with this essential multi-state payroll tax issues 2026 webinar from Professionals...

Simulating Mercury’s Orbital Motion Using Pure T-SQL (NASA 2025 Dataset)

By NKTgLaw

SQL Server is typically viewed as a transactional or analytical database engine. However, it...

Azure SQL Database | CREATE EVENT SESSION [Blocking_Capture] ON DATABASE

By DanielP

Hello, Is there a way in Azure SQL Database to change the 'Blocking Process...

Visit the forum

Question of the Day

String Similarity I

On SQL Server 2025, when I run this, what is returned?

SELECT EDIT_DISTANCE_SIMILARITY('SQL Server', 'MySQL')

See possible answers