Comments
Sort by recent activity
Thanks for your post.
Would you be able to show me the table structure for one of these affected objects?
As far as I'm aware, a primary key is a clustered index in SQL Server and you can only have one clustered index on a table. / comments
Thanks for your post.
Would you be able to show me the table structure for one of these affected objects?
As far as I'm aware, a primary key is a clustered index in SQL Server and you can only have...
Yes, you're correct, thanks for putting me right.
However, I still can't reproduce this issue.
I added a clustered index to both the source and target object, but the automatic mapping using the primary key (piTrevor) still ocurred.
I added:
Source:
CREATE UNIQUE CLUSTERED INDEX [Test_s] ON [dbo].[TrevorTEST] ([ID], [TrevorTypeID])
Target:
CREATE UNIQUE CLUSTERED INDEX [Test_t] ON [dbo].[TrevorTEST] ([ID], [Name], [SortName])
Which exact version of SQL Data Compare 8 are you using? / comments
Yes, you're correct, thanks for putting me right.
However, I still can't reproduce this issue.
I added a clustered index to both the source and target object, but the automatic mapping using the pr...
Thanks for your post.
BLOBS's and (max) data types are not supported as comprison keys in SQL Data Compare. I imagine this is due to performance reasons, as there could potentially be very large amounts of data in the column.
Also, as I understand it, when a MAX data type exceeds a certain size, an overflow page is used. I'm not sure what implications this would have on a comparison key in SQL Data Compare.
I'll see if I can find out exactly why these data types are unsupported and let you know. / comments
Thanks for your post.
BLOBS's and (max) data types are not supported as comprison keys in SQL Data Compare. I imagine this is due to performance reasons, as there could potentially be very large am...
It seems that there is a bug in the native data reader that causes BLOBS and (MAX) data types to be read in their entirety, causing SQL Data Compare to run out of memory and fall over.
We attempted to write our own data reader to get round this problem, but this seemed to introduce more problems than it solved, so we returned to using the native reader.
For this reason BLOB's and (MAX) data types are not supported for comparison keys in the current version.
Hopefully it is something that can be addressed in a future version, but currently it isn't possible. / comments
It seems that there is a bug in the native data reader that causes BLOBS and (MAX) data types to be read in their entirety, causing SQL Data Compare to run out of memory and fall over.
We attempted...
That's right. As soon as the internet connection is lost, the sync' will fail and rollback. / comments
That's right. As soon as the internet connection is lost, the sync' will fail and rollback.
Thanks for your post.
By default, SQL Data compare 8 will put the whole script in a single transaction. This means if there is any problem during the execution of the script the whole script will be rolled back.
You can customise this, so there are two alternatives if you do not want the script in a single transaction.
1) Set the project option 'Don't use transactions in the synchronization script'
2) You can also set the 'Application option' to 'Split transactions' over a certain size. This will result in multiple transactions, so the complete sync cannot be rolled back entirely.
I hope this helps. / comments
Thanks for your post.
By default, SQL Data compare 8 will put the whole script in a single transaction. This means if there is any problem during the execution of the script the whole script will b...
Thanks for your reply, and sorry my suggestion didn't help.
I've only seen this happen before with the kill existing connections option, so would you be able to post your restore script and I will see if there is anything else that could be causing this behaviour.
If you are using the restore wizard, you can find the script on the last step of the wizard. / comments
Thanks for your reply, and sorry my suggestion didn't help.
I've only seen this happen before with the kill existing connections option, so would you be able to post your restore script and I will ...
Thanks for your post.
Can you confirm the restore script you are using. I have seen this issue before when using the 'Kill existing connections' option in the restore script.
We have a bug open for that issue, which is fixed in the next release (SB-4446).
Can you try performing the FULL + DIFF restore without the 'kill existing connections' option and see if it helps? / comments
Thanks for your post.
Can you confirm the restore script you are using. I have seen this issue before when using the 'Kill existing connections' option in the restore script.
We have a bug open for...
Thanks for your post.
When you first map the tables together, all the columns will be mapped by default - e.g.
mappings.CreateMappings(db1.Tables, db2.Tables);
You can then exclude specific columns by setting the FieldMapping include property to 'false'.
We have an example on our website of excluding a column with a specific name from all tables in the project, but you can easily change it to exclude columns from a specific table.
You can find the example here
I hope this helps. / comments
Thanks for your post.
When you first map the tables together, all the columns will be mapped by default - e.g.
mappings.CreateMappings(db1.Tables, db2.Tables);
You can then exclude specif...
Thanks for your post.
I have reproduced this using the steps you outlined, and have logged a bug with the reference code SP-2890.
It only seems to be the keyword 'Select' that isn't suggested, as after you finish typing Select manually, the suggestions start appearing again.
You can also resolve this by adding a GO after the first select statement.
Thanks for taking the time to report this. / comments
Thanks for your post.
I have reproduced this using the steps you outlined, and have logged a bug with the reference code SP-2890.
It only seems to be the keyword 'Select' that isn't suggested, as a...