Deployment issues with Defaults, triggers, and indexes


Author
Message
Matt Tabone
Matt Tabone
StrataFrame Novice (76 reputation)StrataFrame Novice (76 reputation)StrataFrame Novice (76 reputation)StrataFrame Novice (76 reputation)StrataFrame Novice (76 reputation)StrataFrame Novice (76 reputation)StrataFrame Novice (76 reputation)StrataFrame Novice (76 reputation)StrataFrame Novice (76 reputation)
Group: Forum Members
Posts: 16, Visits: 102
We're having an issue with the DDT when making changes to a field. If there is a default value and running for the first time to create the database, then the default is set. If later a change is made to that field and those changes deloyed to the same database, then the default is removed from that field in the database. Even running another time shows the field default as blank when the DDT still has the default value set.

The other part with indexes and triggers is more of a question regarding procedure. It appears that indexes and triggers are always dropped and created even if there were no changes to a particular table. Is this typical?
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search