Comments
Sort by recent activity
I think we may have a patch avaliable that fixes the above issue. At least the patch fixes the problem I was able to reproduce on my server.
If you would like to try it, you can download it from here
Let me know how you get on. / comments
I think we may have a patch avaliable that fixes the above issue. At least the patch fixes the problem I was able to reproduce on my server.
If you would like to try it, you can download it from he...
Thanks for your post.
I've tried to reproduce this, but I don't seem to experience the same symptoms.
Are you generating the script through the UI or the command line interface? Are you unchecking the 'different' and 'target only' rows from the comparison results before you run through the sync wizard?
Have you set a WHERE clause filter in the comparison?
Finally, which exact version of SQL Data Compare (Help > about) are you having this problem with? / comments
Thanks for your post.
I've tried to reproduce this, but I don't seem to experience the same symptoms.
Are you generating the script through the UI or the command line interface? Are you unchecking ...
I'm writing to let you know that we now have a patch version of SQL Data Compare 8 that addresses the issue of writing BLOB data to FILESTREAM.
The issue was that SQL Data Compare would perform numerous partial updates when writing BLOB data; this was implemented to improve performance and memory usage. The current version of SQL Server does not support partial updates to FILESTREAM and therefore the script would fail. The fix in the patch version, now means that the update to the FILESTREAM BLOB happens in one go.
The caveat is that you might find this impacts on the performance and/or memory usage, but since it didn't work at all before, it should be an improvement.
For a download link to the patch, see below: http://www.red-gate.com/messageboard/vi ... hp?t=10917
I hope this helps. / comments
I'm writing to let you know that we now have a patch version of SQL Data Compare 8 that addresses the issue of writing BLOB data to FILESTREAM.
The issue was that SQL Data Compare would perform num...
Thanks for your post.
There are a couple of ways that you could achieve this.
1) The simplest, is to run a comparison and then on the results grid:
- Right-click 'Exclude all different'
- Right-click 'Exclude all Target'
2) You could write a WHERE clause to put on each table. e.g.
id not in (select id from db2.table)
- This is done on the 'Tables & Views' Tab
3) You could use the command line interface using the /include:Missing switch. (http://www.red-gate.com/supportcenter/C ... 700076.htm)
I hope this is helpful. / comments
Thanks for your post.
There are a couple of ways that you could achieve this.
1) The simplest, is to run a comparison and then on the results grid:
- Right-click 'Exclude all different'
- Right-cli...
Thanks for your post.
SQL Compare should detect this difference with the default options.
Can you check that you don't have 'ignore' > 'Full-text indexing' selected? / comments
Thanks for your post.
SQL Compare should detect this difference with the default options.
Can you check that you don't have 'ignore' > 'Full-text indexing' selected?
Thanks for your post.
I agree with what your saying and I've logged this as a bug with SQL Compare. The SEED value should be preserved when the table needs to be rebuilt. Thanks for bringing this to our attention. The bug is logged under the code SC-4615.
This only seems to be a problem if you delete rows from the end of the table.
I will let you know when we find out if/when a fix will be avaliable. / comments
Thanks for your post.
I agree with what your saying and I've logged this as a bug with SQL Compare. The SEED value should be preserved when the table needs to be rebuilt. Thanks for bringing this t...
Thanks for your post.
They’re the index for that set of data scripts – so that we can query them like an indexed table rather than having to read the entire file at once and compile the indexing information ourselves each time. / comments
Thanks for your post.
They’re the index for that set of data scripts – so that we can query them like an indexed table rather than having to read the entire file at once and compile the indexin...
Thanks for your post.
Unfortunatly, it's not possible to add a prefix to the object script filename.
As the objects are grouped by type, I don't think it was ever considered that a prefix would be necessary.
I would be happy to log a feature request if you would like it to be considered for a future version.
Let me know what you think.
You could possibly write a batch file that takes the folder name, and then prefixes all the scripts within the folder with the folder name. / comments
Thanks for your post.
Unfortunatly, it's not possible to add a prefix to the object script filename.
As the objects are grouped by type, I don't think it was ever considered that a prefix would be ...
I'm not really sure. A matching PK should be enough.
I would imagine that this situation wasn't tested for, so nothing has been added to handle a mismatched index like this.
If it would be sufficient, I can log this as a bug with SDC which can be looked at for the next release.
Let me know what you think. / comments
I'm not really sure. A matching PK should be enough.
I would imagine that this situation wasn't tested for, so nothing has been added to handle a mismatched index like this.
If it would be sufficie...
I can reproduce this now, thanks for the info.
It seems that the difference in the index makes it hard for SDC to decide what to use. If you sync the two schemas using SQL Compare first, then the tables will be automatically mapped in SQL Data Compare. / comments
I can reproduce this now, thanks for the info.
It seems that the difference in the index makes it hard for SDC to decide what to use. If you sync the two schemas using SQL Compare first, then the t...