davec wrote:The problem is only fixed by an existance check if you're doing a drop and create with the check being for the drop.
I'm currently working on building a data dictionary into the schema using extended properties. So that is my immediate need.
So I guess from your application point of view, the option only applies if you turn of "Modify" and do drop, creates.
ISRAEL wrote:We have the same situation at our company. Sometimes we have to deploy some objects to some customers before the official distribution release. So, if we use the sync script will cause an error. However, if we can have an option, likes Fred said (“if exist… DROP + CREATE”), we can use the same sync script for all of our customers, no matter what they already have the new objects or not.
A feature like that will improve the efficiency of our updates distribution.
Users browsing this forum: Google [Bot] and 0 guests