Hi guys,

  I'm migrating my customer from SCCM 2012 R2 CU3 to R2 SP1 and getting some fatal errors here in the SQL Upgrade process.  Keep in mind this is using the same version of SQL and running the SP1 installer with /testDbUpgrade, for safety!

   Here's the errors:

   Invalid column name 'Product00'. : usp_GetDeviceDetail
   Invalid column name 'OEM00'. : usp_GetDeviceDetail
   Invalid column name 'DeviceClientID00'. : usp_GetDeviceDetail

All of these columns should live under dbo.DEVICE_COMPUTERSYSTEM_DATA, based on the stored procedure.

When I refer to SQL itself on my prod and the DB copy, I don't see any such columns on this table.

Should I be applying CU 4 or 5 before attempting R2 SP1?  We're not down in production, but it is frustrating that I'm having SQL issues.

I've got a clone of Prod running as well in isolation, which I'm currently attempting to upgrade to CU4 before retrying this upgrade.  I'll update this thread with the status, when I see what happens.

Edit: I was able to apply CU4 to my test instance, with the same database.  All is working, I'm now about to apply CU 5.  If this creates the missing columns, then I believe I found the issue.  

T

Edit: I was able to apply CU4 to my test instance, with the same database.  All is working, I'm now about to apply CU 5.  If this creates the missing columns, then I believe I found the issue.  

Should I be applying CU 4 or 5 before attempting R2 SP1?

No, this is not a requirement. If you find that for some reason this did address your issue, you should report it ASAP to CSS or file a bug on connect.

After applying CU5 to this SCCM instance, we still had the install fail for SP1, which makes sense, as at no time did we successfully create those missing columns.

Working through a support call with MS right now, we're going to try adding the extra columns.  However for customer's time/dollar equation, we may opt to rebuild instead.