Comments
Sort by recent activity
Hi Chris
Rolling back the data files for this particular table reproduces the problem - all tables UP UNTIL this one go through fine, then it stalls with the ASYNC_NETWORK_IO wait until I guess SQL Data Compare times out.
I've enabled logging and will email you the log file - hopefully you'll be able to find the problem and fix in case it happens to anyone else in the future.
David / comments
Hi Chris
Rolling back the data files for this particular table reproduces the problem - all tables UP UNTIL this one go through fine, then it stalls with the ASYNC_NETWORK_IO wait until I guess SQL...
Deleting the _Data.sql and _Meta.sql files for the table in question and re-generating them manually solved the issue.
Any thoughts on how they could have become corrupt? They are only ever updated by SQL Data Compare Pro. / comments
Deleting the _Data.sql and _Meta.sql files for the table in question and re-generating them manually solved the issue.
Any thoughts on how they could have become corrupt? They are only ever update...
Everything fine thanks. / comments
Everything fine thanks.
This problem (SDC-1152) has been fixed in the latest cumulative fix. I just downloaded and tested and it now ignores a letter case only change unless you specify case-sensitivity in the options. / comments
This problem (SDC-1152) has been fixed in the latest cumulative fix. I just downloaded and tested and it now ignores a letter case only change unless you specify case-sensitivity in the options.
Is there any update on this? At the moment I'm having to manually add and remove simple records from all our dev and test machines - can't fathom why it won't simply insert or delete records on certain tables due to this error. / comments
Is there any update on this? At the moment I'm having to manually add and remove simple records from all our dev and test machines - can't fathom why it won't simply insert or delete records on ce...
I agree - the patch has not solved this problem. I've now had it occur with a much simpler comparison - just one record needed to be added to a table with a non-identity primary key.
Error appears both in command line and application when trying to update scripts folder, exactly as edockx has described. / comments
I agree - the patch has not solved this problem. I've now had it occur with a much simpler comparison - just one record needed to be added to a table with a non-identity primary key.
Error appears...
Using the "/force" switch with the other switches works a treat - I no longer get the error message and changes are synchronised and save to the script file.
Thanks a lot - now all I need to SQL Source Control to allow my devs to source control data! / comments
Using the "/force" switch with the other switches works a treat - I no longer get the error message and changes are synchronised and save to the script file.
Thanks a lot - now all I need to SQL So...
I'm afraid this still doesn't seem to have fixed it:
[09:40:11]: SQL Compare Command Line V8.2.1.62
[09:40:11]: ==============================================================================
[09:40:11]: Copyright ΒΈ Red Gate Software Ltd 1999-2009
[09:40:12]: Serial Number: 512-001-127930-C3ED
[09:40:12]: Registering data sources
[09:40:19]: Error: Ignored statement found in file
[09:40:19]: C:\TeamCity.BuildAgent\work\32ff79125c1021f6\trunk\Data\dbo.tbAvailability_Data.sql at line 1
... many more "ignored statement" errors followed... / comments
I'm afraid this still doesn't seem to have fixed it:
[09:40:11]: SQL Compare Command Line V8.2.1.62
[09:40:11]: ==============================================================================
[09:40...
Unfortunately the patch doesn't seem to have fixed the problem, although if I add the /ignoreparsererrors switch then I can continue OK.
Of course once it is fixed I'd like to remove this switch so I am alerted of any parser errors. / comments
Unfortunately the patch doesn't seem to have fixed the problem, although if I add the /ignoreparsererrors switch then I can continue OK.
Of course once it is fixed I'd like to remove this switch so...
I'm also having this problem.
The first time I ran sqldatacompare comparing a script folder to a database it ran fine.
I then made some test data changes and ran it again and it correctly compared and synchronized the scripts folder.
Now, every time I run it all the script files generate the error:
"Error: Ignored statement found in file" for every line of the file.
Very annoying as I am in the process of setting up powershell scripts to automate updating our test database.
Any updates on this? / comments
I'm also having this problem.
The first time I ran sqldatacompare comparing a script folder to a database it ran fine.
I then made some test data changes and ran it again and it correctly compared ...