Posted in Admin

Performance Tuning Part -10 -NoCount

Use ‘SET NOCOUNT ON’ in procedures. SQL server writes the number of rows affected to the client by default, which is not useful for application…

Continue Reading... Performance Tuning Part -10 -NoCount
Posted in Admin

Performance Tuning part -9 – Views

Summary: We should use view if and only if it is really necessary. Use of the view causes performance problem because it still fetches the…

Continue Reading... Performance Tuning part -9 – Views
Posted in Admin

Performance Tuning Part-8-Temporary tables

Tuning Tip: Always create the index after dumping the data in to temporary tables. Loading the data after index creation takes more time and causes…

Continue Reading... Performance Tuning Part-8-Temporary tables
Posted in Admin

Performance Tuning part -7-Print Statement

Do not use the print statement in production (If required, use variable to capture the message for logging). Developers often use print statement to debug…

Continue Reading... Performance Tuning part -7-Print Statement
Posted in Admin

Performance tuning Part -6-correlated sub-queries

Avoid correlated sub-queries. Correlated sub-queries cause more reads and increase the overall execution time. Demo Note: AdventureWorks2017 database has been used for this demo First…

Continue Reading... Performance tuning Part -6-correlated sub-queries
Posted in Admin

Performance Tuning Part 5- Variable Declaration

Define variable with the proper data type. Improper data type may cause conversions which is not good for performance. Execution plan As you can see,…

Continue Reading... Performance Tuning Part 5- Variable Declaration