Potential SQL Refactor Bug...
joliver
Posts: 2
I'm a registered owner of SQL Refactor. We're using v1.10.2.0 (the latest version).
When doing a table rename it appears to lose some of the properties of the table.
For example, if I were to rename my table in SQL Server Management Studio and my table name were [dbo].[Users] and I wanted to rename to [dbo].[Members] the refactor would generate the script to execute in a transactional context (as it should). However it drop the following items and not re-create them:
1. All check constraints that we've added to the table. Note that the default constraints (default values) are kept just fine.
2. Foreign key constraint extended properties (such as descriptions).
Any thoughts or potential workarounds?
Thanks,
J
When doing a table rename it appears to lose some of the properties of the table.
For example, if I were to rename my table in SQL Server Management Studio and my table name were [dbo].[Users] and I wanted to rename to [dbo].[Members] the refactor would generate the script to execute in a transactional context (as it should). However it drop the following items and not re-create them:
1. All check constraints that we've added to the table. Note that the default constraints (default values) are kept just fine.
2. Foreign key constraint extended properties (such as descriptions).
Any thoughts or potential workarounds?
Thanks,
J
Comments
Thank you for your post into the forum.
I have been able to recreate the fault symptoms you described in your post.
I believe you have discovered a bug in SQL Refactor and I will report the details of this problem onto the development team.
Thank you for bringing this problem to our attention.
Many Thanks
Eddie
Eddie Davis
Red Gate Software Ltd
Technical Support Engineer
Senior Product Support Engineer
Redgate Software Ltd
Email: support@red-gate.com
I just realized that my Check Constraints were getting dropped when I did the Smart Rename. This is a big deal! Especially since it is easy to not realize that these things have been dropped.
Please advise regarding the status. Is it fixed in v1.1?