• TheSQLGuru (4/11/2013)


    Thanks for the feedback on this. Did they post a public hotfix yet or is it still a private build? If the latter, please post the link here.

    It is still a private build. Below is the email we received from the MS Development team.

    "We are done with the data analysis and have confirmed that this behavior is a bug. We have a private fix for this issue available now. Do you have a test environment on which we can validate this fix? Assuming the issue is reproducible in your test environment."

    If anyone else is experiencing this issue, feel free to PM me offline and I can provide our SR number. Might save some time when contacting MS.