Why recreate instead of rename?
Fenske
Posts: 3
Dear Support,
i have a question regarding the generated syncronizing script.
I have an example:
The resulting synchronisation script does the following:
My question is: Wouldn't it be wiser (and a lot faster) if the alteration script only renames the index as all other parameters are equal?
It's kind of a showstopper to us as we need to synchronise very large tables and recreating doesn't qualify for the perfect solution.
i have a question regarding the generated syncronizing script.
I have an example:
left side: CREATE NONCLUSTERED INDEX [Name_Vorname] ON [dbo].[Inter] ([Name], [Vorname]) right side: CREATE NONCLUSTERED INDEX [Name] ON [dbo].[Inter] ([Name], [Vorname])
The resulting synchronisation script does the following:
DROP INDEX [Name] ON [dbo].[Inter] CREATE NONCLUSTERED INDEX [Name_Vorname] ON [dbo].[Inter] ([Name], [Vorname])
My question is: Wouldn't it be wiser (and a lot faster) if the alteration script only renames the index as all other parameters are equal?
It's kind of a showstopper to us as we need to synchronise very large tables and recreating doesn't qualify for the perfect solution.
Comments
I'm not sure of any more detailed reason as to why it would be more inefficient in SQL Compare unfortunately as that's all that was written on the request, but it sounds like performing the rename could actually make the problem worse and we have no plans to fix it.
Redgate Software
With kind regards,
Fenske