SSDT Fails to deploy XPath case sensitive fixes

SSDT Fails to deploy XPath case sensitive fixes by Jeff Fischer

Closed

as Won't Fix Help for as Won't Fix

Type:	Bug
ID:	778893
Opened:	2/9/2013 10:33:34 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

SSDT SqlPackage.exe does not recognize case sensitive updates. Therefore, it fails to deploy case-only xpath updates to scripts.

Details (expand)

English

SQL Server 2012 - Express Edition

Data-Tier Application Framework (Dac, DacFX, DACPAC)

Windows Server 2008 (all editions)

US English

Create and deploy the following stored procedure within an SSDT project.

CREATE PROC dbo.TestXPath
As
    DECLARE @TestXml xml = '<Test><Case><Sensitive>Yes</Sensitive></Case></Test>'

    SELECT @TestXml.value('(/Test/Case/sensitive)[1]', 'nvarchar(100)')
GO

Execute the proc and notice NULL result. Fix the casing of the Sensitive element in the xpath expression. Redeploy and re-execute. Notice the NULL results still.

Necessary case-only updates within SSDT projects are not deployed when case is the only update made.

All updates no matter whether case only or not should be deployed independent of whether the SQL Server is set to be case sensitive or case insensitive.

X64

0 attachments

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