Comments
Sort by recent activity
There is an option to "Disable Foreign Keys" before inserting the new data. This is not an ideal way but it will work if you can accept for the foreign keys relationships to be disabled for the duration of the modification to the data. / comments
There is an option to "Disable Foreign Keys" before inserting the new data. This is not an ideal way but it will work if you can accept for the foreign keys relationships to be disabled for the du...
Bug reproduced by the Red-Gate's support team and logged with the reference SDC-907. It will be looked at in the next release of SQL Data Compare although there is no timescales for this at present.
As for the request for the new features, they have been logged with the reference SDC-908 and will be considered for a future release of SQL data Compare.
This thread is now closed.
Thanks everyone.
S. L. / comments
Bug reproduced by the Red-Gate's support team and logged with the reference SDC-907. It will be looked at in the next release of SQL Data Compare although there is no timescales for this at presen...
Andrew Hodge wrote:
... A useful tool that doesn’t seem to be well developed by anyone else ...
Not sure what you mean exactly with the expression "well developed". There is already an application covering this: http://www.sqlimageviewer.com/ ; however, if what you want is a full blow image editor then you should use a dedicated image application such as Paint Shop Pro or Photoshop.
Sylvain Lafontaine, ing. / comments
Andrew Hodge wrote:
... A useful tool that doesn’t seem to be well developed by anyone else ...
Not sure what you mean exactly with the expression "well developed". There is already an appli...
And of course, I suppose that for one reason or another, you cannot include the other table(s) into the synchronisation process.
One possible solution would be to selectively disables the triggers yourself before making/calling the synchronisation process or you could replace these triggers with DRI.
The first solution should be easy to implement by doing a cut&paste or using the command line utility or the SQL-Toolkit. As for the second solution, it's up to you. / comments
And of course, I suppose that for one reason or another, you cannot include the other table(s) into the synchronisation process.
One possible solution would be to selectively disables the triggers ...
I don't know about the table sync order but there is an option to disable the DML triggers before making the sync.
(In the case of DRI, the Disable foreign keys should be checked. There is also an option for dropping the primary keys, indexes and unique constraints which is often useful, especially when you are not using the Reseed identity columns option.). / comments
I don't know about the table sync order but there is an option to disable the DML triggers before making the sync.
(In the case of DRI, the Disable foreign keys should be checked. There is also an...
Hi, just a word to say that I've just removed SQL-Backup (and rebooted) but still no luck, SQL-DataCompare 6 keeps crashing. / comments
Hi, just a word to say that I've just removed SQL-Backup (and rebooted) but still no luck, SQL-DataCompare 6 keeps crashing.
Hi, the crash occurs after the display of the first dialog window of the wizard: it display it's dialog window then after 2 or 3 seconds, the crashing window appears. It looks like that SQL-Compare is trying to access a null record; if I enter the CLR Debugger, I have the following information:
An unhandled exception of type 'System.Data.SqlType.SqlNullValueException' occurred in System.Windows.Forms.dll
Additional information: Data is Null. This method or property cannot be called on Null values.
To my knowledge, there is no further usefull information from the Debugger. If I take a look at the error report (the one to be sent to Microsoft); I have the following content:
from the Error Report Contents; first window:
Error Signature:
EventType: clr20r3
P1: redgate.sqldatacompare.ui.exe
P2: 6.0.0.1124
P3: 4703485d
P4: system.windows.forms
P5: 2.0.0.0
P6: 461ef203
P7: 150c
P8: 12f
P9: desIn42ebwmodxjic4snf0cyehcagzn
If I click to view the contents of the error report:
Exception Information
Code: 0x0434f4d Flags: 0x000000007c812a5b
Record: 0x0000000000000000 Address: 0x000000007c812a5b
Module 1
RedGate.SQLDataC
Image Base: 0x11000000 Image Size: 0x00000000
..... / comments
Hi, the crash occurs after the display of the first dialog window of the wizard: it display it's dialog window then after 2 or 3 seconds, the crashing window appears. It looks like that SQL-Compar...
I must add to that that the wizard seems to be working correctly as I can click the buttons and follow the sequence of dialog windows and even perform the final synchronisation step correctly. / comments
I must add to that that the wizard seems to be working correctly as I can click the buttons and follow the sequence of dialog windows and even perform the final synchronisation step correctly.
Hi, the target machine is SP4 (8.00.2039, Desktop Engine, this is the local instance running on my machine (WinXP Pro SP2)) but the source is running SP3, 8.00.760, Enterprise Edition.
Does your solution relates to the version of the source, the target or to either one of them? / comments
Hi, the target machine is SP4 (8.00.2039, Desktop Engine, this is the local instance running on my machine (WinXP Pro SP2)) but the source is running SP3, 8.00.760, Enterprise Edition.
Does your so...
Yes, I had SQL Backup Pro (july 2006) installed on this machine and removed a few weeks ago and SQL Backup 5 installed recently but never used.
If I remember correctly, I've used SQL Backup Pro (the older version) to make some tests but not with this particular database; it was with another database running on the same instance.
I'd also used SQL Log Rescue but again not on this database, it was on another one but still both on the same (target) SQL-Server 2000.
I can try removing SQL Backup 5 (and/or SQL Log Rescue) if you think this might help correcting the problem. / comments
Yes, I had SQL Backup Pro (july 2006) installed on this machine and removed a few weeks ago and SQL Backup 5 installed recently but never used.
If I remember correctly, I've used SQL Backup Pro (th...