Comments
Sort by recent activity
Don't worry, it's still in our list to fix - this is just an early access release to get some initial feedback on the scripts functionality, not anything as advanced as a beta yet [image] . / comments
Don't worry, it's still in our list to fix - this is just an early access release to get some initial feedback on the scripts functionality, not anything as advanced as a beta yet .
Comparison would be extremely slow for even moderately large files without the .sdcs, just because it takes considerable time to search / randomly access large files - the metadata files are not just a compressed copy of the data, they're a representation of the available indexes so that you can use different comparison keys with the script tables without an enormous performance hit.
Even if we didn't have metadata files, we still wouldn't be supporting free hand-modification of the data for this release - we'd like to get it out sometime this year and getting the parser to handle user-edited files up to our normal quality standards would make this unlikely [image] .
What did you want to do with the data that the .sdcs files / no-hand-editing restriction makes impossible? It might be that we can provide some kind of workaround, or at least we can note it down for a subsequant release. / comments
Comparison would be extremely slow for even moderately large files without the .sdcs, just because it takes considerable time to search / randomly access large files - the metadata files are not ju...
This feature is unlikely to make SQL Data Compare 8.0, I'm afraid - we're already at our quota of extra features that need UI work. / comments
This feature is unlikely to make SQL Data Compare 8.0, I'm afraid - we're already at our quota of extra features that need UI work.
Which version (i.e. 7.0, 7.1, 7.2) of SQL Compare are you using?
If it's one with the logging functionality in, you should be able to access the engine log from the 'icon menu' (the menu off the SQL Compare icon in the very top left of the window). If you set the logging to 'verbose', it should give you information about what object is causing it to fail and hopefully also a stack trace you can send us, which might help us work out what's gone wrong.
If it's an earlier version without the built-in logging, it might still be possible to turn on logging in a more manual fashion - I can give you instructions for that if necessary. / comments
Which version (i.e. 7.0, 7.1, 7.2) of SQL Compare are you using?
If it's one with the logging functionality in, you should be able to access the engine log from the 'icon menu' (the menu off the SQ...
That sounds like it was just taking a long time to read the database, yes.
It's likely to be limited by the speed of the connection to the database server (if over a network) and/or the writing speed to where you're writing temporary files to (which you can change if necessary by adding a 'RGTEMP' environment variable with the new path), which you might be able to improve to get the speed up a little, but a database that size will take quite some time to read in any case. / comments
That sounds like it was just taking a long time to read the database, yes.
It's likely to be limited by the speed of the connection to the database server (if over a network) and/or the writing spe...
Hmm. That behaviour means that the synchronization dialog is throwing an exception. I thought we'd managed to get rid of them all - I'm sorry that you've been inconveinenced by digging this one up. Could I get a few more details, please?
1) Are you comparing two live databases, or some other combination of data source types?
2) Which synchronization method do you have selected with the radio buttons at the side (create a synchronization script or synchronize using SQL Compare), and what options do you have checked / what's in the text boxes on the page you can't advance from?
3) Do you have v7, and can you get to the 'dependencies' page in the v7 synchronization wizard without any problems? If you can, are there any dependencies listed? Are you trying to synchronize just some objects from the databases, or all of them?
Hopefully something there will shine light on what's causing the exception and we can reproduce it locally and get it fixed for you [image] . / comments
Hmm. That behaviour means that the synchronization dialog is throwing an exception. I thought we'd managed to get rid of them all - I'm sorry that you've been inconveinenced by digging this one up....
Which behaviour do you prefer? We'll be updating Data Compare to bring the controls in line with the improvements in SQL Compare 8, so this is one of the things where we might fix the inconsistancy. / comments
Which behaviour do you prefer? We'll be updating Data Compare to bring the controls in line with the improvements in SQL Compare 8, so this is one of the things where we might fix the inconsistancy.
Have you selected any objects in the project? When using a project from the command line, it obeys object selections that you made in the UI - but by default nothing starts out selected to avoid accidental deployments, so if you didn't select any objects, you will be left in the situation you describe. You should be able to fix this by re-opening the project in the UI and selecting all objects. / comments
Have you selected any objects in the project? When using a project from the command line, it obeys object selections that you made in the UI - but by default nothing starts out selected to avoid ac...
It's not useful with a project file - it takes effect with include/exclude options specified on the command line. / comments
It's not useful with a project file - it takes effect with include/exclude options specified on the command line.
Unfortunately the problem is much more likely to be caused by a combination of product installs rather than the SQL Search version, so updating other products installed in SSMS is much more likely to help than attempting to roll back SQL Search; installing a previous version of SQL Search would just auto-update back to this version in any case. / comments
Unfortunately the problem is much more likely to be caused by a combination of product installs rather than the SQL Search version, so updating other products installed in SSMS is much more likely ...