In this case post installation of SQL Server 2016 SP1, it is recommended to uninstall the ODBC Driver installed by SQL Server 2016 SP1 and install.To check for ODBC Driver installed on the server, you can go to Control Panel of the server – Programs and Features – Search for ODBC. If you have installed ODBC Driver 13.1 on your server for any reason, SQL Server 2016 SP1 installation overrides the ODBC Driver 13.1 installation and the fixes introduced in 13.1 like may be lost. The issue and error below is applicable only to SQL Server 2016 branches patched with Security Update, CU3 or SP1 and doesn’t apply to lower versions of SQL Server.“This business rule contains corrupted rule item(s), as corresponding SQL Script has been changed”“The sequence must be greater than zero”The fix for this issue is included in the following updates.ODBC Driver 13.1With the default installation of SQL Server 2016, ODBC Driver 13.0 is installed on the server which is used by SQL Agent and SSMS (installed on server) to connect to the SQL Server instance. This issue is introduced by fix in GDR which is also included in SQL Server 2016 SP1 and SQL Server 2016 CU3. The issue is under investigation but users if hit it, they can use the workaround described in.We confirm that SSIS is not impacted by the abovementioned issue in SQL Server 2016 SP1.SQL Master Data Services (MDS)After installing SQL Server 2016 SP1, when you try to add or edit a business rule, it fails with error below.

Sp1 error c000003a