SP1 domain based attribute with change tracking enabled causes SYSERR245 - by GregGalloway

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 771245 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 11/15/2012 7:27:45 AM
Access Restriction Public


After applying SQL2012 SP1, if you have a MDS model which contains a domain based attribute with change tracking enabled, when you try to load data via the staging table, you get the error:

SYSERR245|Conversion failed when converting the nvarchar value 'YourValueHere' to data type int.
Sign in to post a comment.
Posted by EthernetIP on 11/5/2013 at 1:20 PM
Ok, Just applied the updated, and it did NOT fix the issue.
Disabling Tracking on the Domain-Based Entity did, but that is not an option.
Posted by Microsoft on 1/30/2013 at 3:57 PM
Please see KB article
with link to download the update. Thank you for reporting or voting on the issue and your patience while we get the fix out.
Posted by Allxone on 12/4/2012 at 10:04 AM
I'm very disappointed by not having a temporary workaround. I had some troubles due to this bug and disabling Change Tracking is not an option for me. Looking at sp mdm.udpEntityStagingCreateLeafStoredProcedure I can see it is really a simple to solve bug, basically based on completely skipping the testing phase. Really strange it is included in a so called "highly tested service pack", probably MDS does not deserve so much attention by SQL Server testers.

Posted by Microsoft on 11/27/2012 at 8:36 AM
Hi Greg,

Thanks for the feedback. We’re closing this issue as “Fixed” as we have identified the problem and will address it in the next post-SP1 cumulative update for SQL Server 2012.