Questions[service-pack](server)

Installation of SQL Server 2014 SP1 fails if you have as SSIS Catalog on your server. After that, server does not start. Rebuilding system databases did not help (not sure, maybe because system databases were not actually corrupted, hence they were not really rebuilt maybe).

There's a bug in the script SSIS_hotfix_install.sql which ships with SP1 on line 3188:

CREATE NONCLUSTERED INDEX [IX_internal_object_parameters_inc] ON [internal].[object_parameters]

They used a 2-part name for the table while the script which is supposed to upgrade SSISDB is executed in the master database.

The script can by default be found in C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Install , but apparently they do not take it from there for execution upon server startup.
They probably take it from sqlscriptupgrade.dll found in C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Binn. Does anybody know how to bypass execution of that script and get server to start?

Usually Windows shows SPX on the System Information screen - is that the case for Windows Server 2008 R2? Is this a reliable way to verify whether or not SP1 is installed on this machine?

Slipstreaming Windows service packs used to be a simple process with earlier versions - just run the EXE with a special command-line switch. I can't seem to find such a switch with Windows Server 2008 R2 service pack 1. How do I slipstream it? TechNet mentions "integrated installation", so it's possible, but it doesn't seem to have any details on how to actually do it!

I am about to request a hotfix for Windows 2003 Server. As far as I am aware there is no publicly available Service Pack 3. However on the hostfix request page I see this:

I am guessing this is a mistake?

I am trying to install SQL Server 2005 Service Pack 3 and it keeps failing. Comes back with the following:

Microsoft SQL Server 2005 - Update 'Service Pack 3 for SQL Server Database Services 2005 ENU (KB955706)' could not be installed. Error code 1603.

The detailed dump reveals the following:

MSI (s) (90:C8) [13:50:17:776]: Note: 1: 1729 MSI (s) (90:C8) [13:50:17:776]: Transforming table Error.   
MSI (s) (90:C8) [13:50:17:776]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (90:C8) [13:50:17:792]: Transforming table Error.   
MSI (s) (90:C8) [13:50:17:792]: Transforming table Error.    
MSI (s) (90:C8) [13:50:17:792]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (90:C8) [13:50:17:792]: Transforming table Error.    
MSI (s) (90:C8) [13:50:17:792]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (90:C8) [13:50:17:792]: Transforming table Error.    
MSI (s) (90:C8) [13:50:17:792]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (90:C8) [13:50:17:792]: Transforming table Error.
MSI (s) (90:C8) [13:50:17:792]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (90:C8) [13:50:17:807]: Transforming table Error.    
MSI (s) (90:C8) [13:50:17:807]: Transforming table Error.    
MSI (s) (90:C8) [13:50:17:807]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (90:C8) [13:50:17:807]: Transforming table Error.  
MSI (s) (90:C8) [13:50:17:807]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (90:C8) [13:50:17:807]: Transforming table Error.  
MSI (s) (90:C8) [13:50:17:807]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (90:C8) [13:50:17:807]: Product: Microsoft SQL Server 2005 -- Configuration failed.

Does it mean anything to anybody?

Btw, this Q originally came from SO (936895)