For the second part of this series, I’m relying on a project hosted on codeplex which can be found by the name TSQL Code Smells Finder. The solution consists out of 3 files (one PowerShell script, a text file containing a list with possible errors and a whitelist file) and build within PowerShell, therefore it’s not that complicated to extend the solution later.
When moving a new SQL server database into production or taking over maintenance duties for large and heavenly used databases, you might want to perform some audit’s allowing you to ask some additional questions when the development team is still available or just being aware of possible performance issues / special maintenance routines etc.
Probably one of the most common issues customers run into after completing the upgrade is performance degradation. This post covers how you can identify and solve SQL Server related issues after upgrading to a newer version.
Recent Comments