learning from experience
In SQL Server, there are various scenarios in which you may want to consider recompiling a query or a stored procedure to ensure optimal query performance. Recompilation generates a new query execution plan, and it can be necessary when the existing execution plan is no longer suitable.
Last week, in the post Common Mistakes in SQL Server – Part 4 I explained about the Auto Growth configuration in SQL Server and how it can adversely impact. This week, I am going to explain a very important thing that is often skipped. It is a common mistake that can indeed lead to performance problems. Implicit Conversion can cause unexpected performance issues and hinder query optimization. This week in Common Mistakes in SQL Server – Part 5 let’s speak about the Implicit Conversion.
Last week we have discussed how Null Values can cause a trouble in Common Mistakes in SQL Server – Part 3. This week I would like to draw your attention to a database configuration that is often missed. If this value is not configured with care, it can cause I/O and CPU spike, and can also cause physical fragmentation.
The Identity property creates an incremental value for the specified column automatically, which is why it is widely used by developers when they designed the table and a primary key – an identifier column. This is the Common Mistakes in SQL Server Part 2