When changing a table to a view Schema Compare does not drop table first, and then create view.
Could it interpret the order to take same-named objects?
4
votes
![](https://secure.gravatar.com/avatar/dbcfe2f55473cf8a441933254412c43b?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
-
Darren Ferris commented
I also have this problem when replacing a table with a view of the same name. It tries to create the view before dropping the table and fails with a ORA-00955 name is already used by an object error.
This can also happen when changing a stored proc to a function and vice versa. -
AdminRichard Mitchell (Admin, Redgate) commented
I take it that sometimes we don't clear out the pre-existing object name before creating the new name that clashes.
-
Mike commented
It appears this sometimes works so the drop must have been ran first in that instance.