Another SQL Server upgrade failure: upgrade step SSIS_hotfix_install.sql hit error 15151 because a user did not exist. Here is how I fixed it.
ISSERVER Assembly Upgrade Error: Cannot Drop the Assembly (Msg 15151 and 6528)
An ISSERVER assembly error during a SQL Server upgrade needs the surrounding SSISDB messages before you choose a repair. The tests here trigger both errors in a throwaway database, show how they differ and run the catalog checks safely when SSISDB is missing or unreadable.
SQL SERVER – Cannot Drop the Assembly ‘ISSERVER’, Because it Does not Exist or You do not Have Permission
An upgrade could not start SQL Server: Cannot drop the assembly ‘ISSERVER’, because it does not exist or you do not have permission. Here is another way to fix it.
SQL Server Integration Services (SSIS) – There Was an Exception While Loading Script Task from XML
An SSIS package ran fine in Visual Studio but failed as a SQL Agent job: There was an exception while loading Script Task from XML. Here is why and the fix.
SQL SERVER – Huge Size of SSISDB – Catalog Database SSISDB Cleanup Script
SSISDB grew huge on a client’s server. Here is my cleanup script for the SSISDB catalog database, and why I avoid scripts that modify system objects.
SQL SERVER – SSIS – Package Error: “ODBC Source” Failed Validation and Returned Validation Status “VS_NEEDSNEWMETADATA”
A client’s SSIS package failed: “ODBC Source” failed validation and returned validation status “VS_NEEDSNEWMETADATA”. I explain which metadata and the fix.
Integration Services Evaluation Period Has Expired: Maintenance Plan Fails
The Integration Services evaluation period can expire while the Database Engine keeps running, and the maintenance plan that depends on it fails. In one client case backups stopped. These checks show how to find the failure, close the backup gap and identify the expiring component.