You can reproduce this bug with the following steps:
1. create a new database
2. create a new table with four columns
id int
a int
b int
c is a computed column(c=a+b)
3. create a new clustered index on table
and the index key columns is column id and column c
4. import the datbase with table and index into sql source control
5. modify the column type of column b to bigint
6. commit the change of column b
7. use sql compare to genrerate sql scripts about step 5
You will get the scripts like this :
The index was dropped without re-created
Comments
6 comments
-
By the way, the version of sql compare is 13.7 .4 and the version of sql source control is 7.0.11
-
Thanks for your post, @chuck!
I am able to reproduce this and am looking into it- please bear with me. -
Hi @chuck,
I've logged a bug for this with reference SC-10449 and will let you know once we have an update. -
Hi @chuck!
I'm happy to report that this issue has been resolved as of today's frequent update release, v13.7.8. Can you please update from Help>Check for updates (you need to make sure that you have frequent updates enabled) and give this a try?
I hope that helps but please let us know if you run into any other issues!
-
Hi @Jessica,I have upgrade the sql compare to 13.7.8, and test it with previous test case.The generated scripts works now, the index was re-created.Thanks.
-
Thanks for confirming, @chuck - glad to hear it helped!
Add comment
Please sign in to leave a comment.