Final Support and SQL Server Upgrade

One of the basic business of DBA is updgrading. And there are lots of work about it. Eliminating the discontinued features is one of big issues.
The first step of this issue is to discover which discontinued feature are used on the system to be upgraded. SQL Server Profiler can be used to discover it. "Deprecation Final Support" event collects this data.

The second step is eliminating the issues. This step may take time and effort if there are lots of issues.

The last but not the least step is to ensure that you have eliminated all the discontinued features. To be sure it can be traced again  "Deprecation Final Support" after elimination. At this point it important to be aware that some internal objects may contain discontinued features. If you miss this you will not be able to find user oject that contains discontinued feature. And this will mislead you as there are some object that stil have discontinued feature even though there is not.
To give an example;
With SQL Server 2012, raiserror syntax has changed as known. If you have linked servers, and if you execute some queries on the remote server, internaly sys.sp_table_statistics2_rowset system procedure is also called. The profiler catches this. If look into this procedures code you will see a line like "raiserror 20001 '~~Rush_5~~'" which is not supported on SQL Server 2012. Even though there is no user code which contains this discontinued feature, the profiler tells you that there is. If you are not aware of this stuation you may continuesly searching for user defined objects for discontinued feature.

No comments:

Post a Comment