After upgrading to SQL Server 2012 SP1, I ran into a bug in Master Data Services (MDS) that applies only to models that are deployed or created after SP1 is applied (models deployed or created before SP1 is applied are fine): When executing a staging entity load stored procedure (i.e. udp_[Model]_[EntityName]_Leaf) I get an error:
Msg 50000, Level 16, State 1, Procedure udp_FMD_RefFacilityStatus_Leaf, Line 1431
SYSERR207|Invalid column name ‘uda_314_8158′.
And I see someone has already reported this on Connect: SQL 2012 SP1 schema version 126.96.36.199 Staging Stored Proc for Entity returns SYSERR207|Invalid column name
It seems it also only applies when change tracking is enabled on the Code or Name attribute. This bug also applies if you start a batch via the MDS web UI (but it won’t display an error, it will just not transfer records into MDS).
The two solutions are:
1) Remove change tracking from Code and Name
2) Modify the staging stored procedure as documented in the above Connect item