Comments
Sort by recent activity
Hi Kailash,
Can I ask what version of Compare you are using? We had seen a bug similar to this a few weeks ago and released a fix in version 13.1.3.5405. If you are on a version earlier than this could you try upgrading to the latest version of Compare and seeing if the problem persists?
Thanks,
Asha / comments
Hi Kailash,
Can I ask what version of Compare you are using? We had seen a bug similar to this a few weeks ago and released a fix in version 13.1.3.5405. If you are on a version earlier than this c...
That's interesting. Do you have any records for checking what has changed in your database schemas since they was last successfully compared? Have any of the column types been changed? I'm thinking maybe it's a time column type (https://docs.microsoft.com/en-us/sql/t-sql/data-types/time-transact-sql) that isn't being handled properly, which would also explain why you're seeing the error on the 'Remap Objects' tab.
As an alternative, is it possible for you to upgrade to the latest Data Compare version? We are now on version 13.1.1; version 5.4.0.0 of Data Compare is over 10 years old. There have been a lot of improvements throughout the later versions which may have already handled the issue you are seeing. / comments
That's interesting. Do you have any records for checking what has changed in your database schemas since they was last successfully compared? Have any of the column types been changed? I'm thinking...
Hello,
I'm sorry to hear you're hitting a problem!
Have you managed to successfully compare these two databases before you started seeing this error? If so, has anything changed recently in the schema? / comments
Hello,
I'm sorry to hear you're hitting a problem!
Have you managed to successfully compare these two databases before you started seeing this error? If so, has anything changed recently in the sch...
Hello,
Our apologies for the problem you've encountered.
'SSMS Integration Pack' appears as a separate product to SQL Compare. Please can you try uninstalling 'SSMS Integration Pack Framework' (and if you have it installed 'SSMS Integration Pack') and checking whether you still see a problem? / comments
Hello,
Our apologies for the problem you've encountered.
'SSMS Integration Pack' appears as a separate product to SQL Compare. Please can you try uninstalling 'SSMS Integration Pack Framework' (and...
Hi all, The latest SQL Search version (v 3.2.2) released today should now support Azure AD authentication. / comments
Hi all,The latest SQL Search version (v 3.2.2) released today should now support Azure AD authentication.
Hi Gerardo,
I'm sorry to hear you're hitting this problem!
You are correct in your understanding how the filters work. Setting Options.Default.Plus(Options.IgnoreUsers, Options.IgnoreUserProperties) should indeed ignore any Users and UserProperties differences. I have raised an internal bug report CSD-220 for investigation; we shall update you when we have made any progress.
Again, sorry you encountered this!
Thanks,
Asha / comments
Hi Gerardo,
I'm sorry to hear you're hitting this problem!
You are correct in your understanding how the filters work. Setting Options.Default.Plus(Options.IgnoreUsers, Options.IgnoreUserProperties...
Hello,
SQL Compare should indeed either drop the existing index before creating the new one, or alter the existing one. Could you check the project options you are using to make sure you don't have the "Ignore indexes" option set and let us know if that's solved your problem?
Thanks,
Asha / comments
Hello,
SQL Compare should indeed either drop the existing index before creating the new one, or alter the existing one. Could you check the project options you are using to make sure you don't have...
Ah I see what you mean now. I've tried to replicate but I am seeing the constraint with the default value correctly picked up in the target column. What version of SQL Compare are you running? If you upgrade to the latest version (under Help --> Check for updates) do you still see the same problem?
If you're still hitting the problem could you please email support@red-gate.com; someone will be in touch to investigate further and try to resolve this.
Thanks,
Asha / comments
Ah I see what you mean now. I've tried to replicate but I am seeing the constraint with the default value correctly picked up in the target column. What version of SQL Compare are you running? If y...
Hello,
Sorry to hear you're hitting a problem!
I'm having some trouble reproducing the issue you mentioned. Did you mean your source column is
[PublicHousing] [bit] NOT NULL CONSTRAINT [DF_Interview_PublicHousing] DEFAULT ((0))
and your target column is
[PublicHousing] [bit] NOT NULL
?
I have tried a deployment like this and I can see Compare correctly creating the constraint:
PRINT N'Adding constraints to [dbo].[table]'
GO
ALTER TABLE [dbo].[table] ADD CONSTRAINT [DF_Interview_PublicHousing] DEFAULT ((0)) FOR [PublicHousing]
GO
I don't understand how this is failing due to the named constraint already existing, as the named constraint doesn't exist in the target column. Am I misunderstanding something?
Thanks,
Asha / comments
Hello,
Sorry to hear you're hitting a problem!
I'm having some trouble reproducing the issue you mentioned. Did you mean your source column is
[PublicHousing] [bit] NOT NULL CONSTRAINT [DF_Intervie...
Hi,
Sorry you're having this problem!
This error is thrown whenever a duplicated definition is found that is not solely due to case sensitivity (for instance, definitions for 'UserName' and 'username' would throw a different error). Could you check inside the file 'Scripts.Sql' and see if it has a different definition for 'UserName' defined in there?
If this isn't the case we'd need to look into this further; could you contact support@red-gate.com and attach the scripts you are using to compare against the database, and we shall investigate further.
Thanks,
Asha / comments
Hi,
Sorry you're having this problem!
This error is thrown whenever a duplicated definition is found that is not solely due to case sensitivity (for instance, definitions for 'UserName' and 'userna...