Single Profile Script vs Multiple Profile Scripts?


Author
Message
William Fields
William Fields
StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)
Group: StrataFrame Users
Posts: 80, Visits: 239
Hello,

I know, probably a simple question with an obvious answer... "it depends..."

But, I have a large number of check constraints that I need to add to a DDT profile as deployment scripts and I was wondering what the benefit would be to create separate scripts for each table, or even each constraint, vs a single script for the entire database.

I can see there is a priority level that can be assigned, which would give me flexibility in the order the scripts are applied, but can anyone else chime in on other (not obvious) benefits of the separate vs combined approach?

Thanks.

Bill
Reply
William Fields
William Fields
StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)StrataFrame User (326 reputation)
Group: StrataFrame Users
Posts: 80, Visits: 239
Thanks Edhy.

Off bat, it seems to me that a way to enable/disable individual scripts would be handy for development/testing.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Threaded View

Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search