SSDT Fails to deploy XPath case sensitive fixes - by Jeff Fischer

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<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 778893 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 2/9/2013 10:33:34 PM
Access Restriction Public


SSDT SqlPackage.exe does not recognize case sensitive updates.  Therefore, it fails to deploy case-only xpath updates to scripts.
Sign in to post a comment.
Posted by Jeff Fischer on 2/15/2013 at 10:58 PM
As you know, that's a useless workaround.
Posted by Adam [MSFT] on 2/15/2013 at 8:00 AM
Hey Jeff,

Thanks for the feedback around the case sensitivity of the XPath expressions used in the .value functions in stored procedure bodies. The root cause of this issue is the way we represent stored procedure bodies and compare them using the target db collation. We are not appropriately recognizing the implicit need to be case sensitive inside this part of the proc body.

Unfortunately, due to the priorities of other issues, the team will not be pursuing a fix for this issue. The workaround is to use a case sensitive collation on the target database which will then be used to compare the body of the procedure.

Thanks and please let us know if you have any additional questions,
Adam Mahood
Program Manager
SQL Server Database Systems