Comments
Sort by recent activity
Good news! It looks like our test instance has now received this change, so we should be able to reproduce and figure out how to handle it now (and any other changed columns that might have sneaked in as well [image] Hopefully we'll have a fix out soon. / comments
Good news! It looks like our test instance has now received this change, so we should be able to reproduce and figure out how to handle it now (and any other changed columns that might have sneaked...
Unfortunately it looks like I can't create an Australia East instance with my subscription: [image] / comments
Unfortunately it looks like I can't create an Australia East instance with my subscription:
Ok, I'll try creating an Australia East Sql server instance and see if that makes a difference.
In the meantime, I'm curious what you see for the following query: SELECT
(@@microsoftversion / 0x1000000) & 0xff AS VersionMajor,
(@@microsoftversion / 0x10000) & 0xff AS VersionMinor,
@@microsoftversion & 0xffff AS BuildNumber
SELECT SERVERPROPERTY('productversion') AS ProductVersion
On our test server we get: VersionMajor VersionMinor BuildNumber
------------ ------------ -----------
13 0 702
(1 row(s) affected)
ProductVersion
------------------------
12.0.2000.8
(1 row(s) affected)
@microsoftversion instead... / comments
Ok, I'll try creating an Australia East Sql server instance and see if that makes a difference.
In the meantime, I'm curious what you see for the following query:SELECT
(@@microsoftversion / 0x1000...
Interesting - on our test instance I get
Microsoft SQL Azure (RTM) - 12.0.2000.8 Jan 30 2016 11:11:59 Copyright (c) Microsoft Corporation
Thanks for the update - good to hear that it's working for you again. I believe we are currently asking Microsoft about what happened here, so hopefully we'll have a bit more warning next time [image] / comments
Interesting - on our test instance I get
Microsoft SQL Azure (RTM) - 12.0.2000.8 Jan 30 2016 11:11:59 Copyright (c) Microsoft Corporation
Thanks for the update - good to hear that it's working...
Hi there
Thanks for the report - I'm just looking into this now.
Unfortunately I don't seem to be able to reproduce it from here - I've just re-run all our azure v12 tests and they seem to be happy. The column we're looking for is in sys.tables - what columns do you see there at the moment? / comments
Hi there
Thanks for the report - I'm just looking into this now.
Unfortunately I don't seem to be able to reproduce it from here - I've just re-run all our azure v12 tests and they seem to be happy...
Hi there-
Recently we've been doing some work to remove Syncfusion components from our products, since we believe they no longer provide enough value for their (rather high) licensing costs. Part of the work involved required rewriting the SQL Data Compare differences grid. Unfortunately we have limited resources and we saw that the pivot view had rather low usage, so it didn't make it into this rewrite. If you'd like to see it again I'd encourage you to head over to the SQL Data Compare uservoice page and add it as a suggestion - in particular, it would be useful if you can explain why pivot view is useful to you so that we can build something better if we decide to revisit it.
I'll make sure the relevant release notes get updated, since it looks like we missed updating those. Sorry for the trouble. / comments
Hi there-
Recently we've been doing some work to remove Syncfusion components from our products, since we believe they no longer provide enough value for their (rather high) licensing costs. Part o...
Yep, there's a new /empty2 option you can use: http://documentation.red-gate.com/displ ... ne-/empty2 which means you don't need to set up a blank database yourself. / comments
Yep, there's a new /empty2 option you can use: http://documentation.red-gate.com/displ ... ne-/empty2 which means you don't need to set up a blank database yourself.
Ok, it looks like we've released a couple of fixes in this area (from http://documentation.red-gate.com/displ ... ease+notes):
- 11.5.2.509 - March 15th, 2016 / SC-8138: Asymmetric keys with NA algorithm (e.g. from hardware EKM) no longer cause comparison to fail.
- 11.5.8.1398 - May 3rd, 2016 / SC-8524: support hardware crypto devices (e.g. nCipher) for asymmetric key encryption
so give it another shot with the latest Frequent Updates version and let us know if you're still having problems [image] / comments
Ok, it looks like we've released a couple of fixes in this area (from http://documentation.red-gate.com/displ ... ease+notes):
- 11.5.2.509 - March 15th, 2016 / SC-8138: Asymmetric keys with NA alg...
I'll check up on this - I think we've got a fix in the works which should hopefully be released soon / comments
I'll check up on this - I think we've got a fix in the works which should hopefully be released soon
We should have a fix for this in Data Compare 12.0.14.2614 - apologies for the trouble / comments
We should have a fix for this in Data Compare 12.0.14.2614 - apologies for the trouble