Running SQL Server 2012 Upgrade Advisor on a SQL 2008 R2 SSIS instance got the following errors all pointing to the data collector/MDW packages deployed under SSIS instance. first error is shown as critical the second one as warning. how to upgrade the dc packages in 2008 R2 SSIS instances to 2012, or the next 2 errors can be neglected?
SQL Server Integration Services PostUpgrade
Recompile third-party and custom components to work with SQL Server 2012. In SQL Server 2012, Integration Services has changed its application programming interfaces (APIs). To be compatible with these new APIs, all third-party and custom components may
need to be recompiled. SQL Server 2008 and 2008 R2 components can use assembly binding redirection to continue working in SQL Server 2012. SQL Server 2005 components may require additional code changes to work with SQL Server 2012. Package Name: TSQLQuery_ServerName_MSSQL10_50_MSSQLSERVER_{GUID}_3_Collect
Source Type: Repository Package Location: /MSDB/Data Collector/Generated/TSQLQuery_ServerName_MSSQL10_50_MSSQLSERVER_{Guid}_3_Collect
as well as
SQL Server Integration Services PostMigration
Update provider names in connection strings to be compatible with SQL Server 2012.In SQL Server 2012, connection strings require a different value for some provider names. The value for the SQL Server Native Client provider is now SQLNCLI11. The value for the
OLE DB Provider for Analysis Services is now MSOLAP.5. To automatically update these provider names, use the Package Upgrade tool to upgrade SQL Server 2005 and SQL Server 2008 packages. You can also manually update these names in Business Intelligence Development
Studio.
Package Name: TSQLQuery_ServerName_MSSQL10_50_MSSQLSERVER_{GUID}_3_Collect Source Type: Repository Package Location: /MSDB/Data Collector/Generated/TSQLQuery_ServerName_MSSQL10_50_MSSQLSERVER_{GUID}_3_Collect