February 17, 2015 at 8:44 am
This happens to me occasionally, in different databases with different types of object, and I've finally summoned the energy post here to see whether anyone else experiences the same thing.
I have a database which I am comparing with a VS2013 database project.
Running the comparison results in the display of a single proc.
Drilling into the body of the proc, I see that there are no differences identified between db version and project version.
If I shrug my shoulders and 'Update' anyway, after completing the update and doing another Schema Compare, the proc once again is identified as being different.
Anyone else seen this? Any explanations out there?
By the way, I have 'Ignore whitespace' selected.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
February 17, 2015 at 8:49 am
Yes, I get the same - it's not very helpful is it?
I hope this prompts someone to point out how to spot the difference...
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply