Comments
Sort by recent activity
Thanks James!! You're continuing in the awesome tradition of Redgate's great service. Thanks again!! / comments
Thanks James!! You're continuing in the awesome tradition of Redgate's great service. Thanks again!!
Anuradha-
SQL Server 2008 R2 - 10.50.6220
Database compatibility is SQL Server 2008 (100)
I am comparing from the database against TFS source control. I upgraded to SQL Compare 11.3.0.7 and the error still occurs. I added a note on the sys.asymmetric_keys BOL entry for 2008 R2 (I don't know if this behavior applies to later versions but I suspect it would): https://msdn.microsoft.com/en-us/librar ... (v=sql.105).aspx
The error in SQL Compare is most likely that the 'NA' value in the algorithm column is not listed on BOL. I further suspect that use of hardware EKMs is not widespread and thus this situation is not common. I will be happy to demo via a WebEx, etc.
Thank you for the update.
Alex / comments
Anuradha-
SQL Server 2008 R2 - 10.50.6220
Database compatibility is SQL Server 2008 (100)
I am comparing from the database against TFS source control. I upgraded to SQL Compare 11.3.0.7 and the err...
If anyone is interested, RedGate Support assisted further on how to use SQL Compare to determine the details. In SQL Compare, point to the repository in source control for the database in question as the source and the corresponding deployed database as the target (or vice versa, the order does not matter in this context). Click on Compare Now. If Source Drift is present, an 'Error Parsing Scripts' dialog box will appear. The details cannot be copied and pasted as text, but you can take a screenshot. Alternatively, you can work through each one manually to resolve the issue.
Thank you RedGate Support for your help! / comments
If anyone is interested, RedGate Support assisted further on how to use SQL Compare to determine the details. In SQL Compare, point to the repository in source control for the database in question ...