Question

5
Replies
846
Views
Close popover
Andreas Sittler (SITTA)
PEGA
Principal Solutions Architect
Pegasystems
DE
SITTA Member since 2010 3 posts
PEGA
Posted: November 23, 2016
Last activity: January 20, 2017
Closed

721+ DevOps - Best practice to isolate DB schema changes?

I am looking for best practice to isolate schema changes during deployment.
Is it conceptionally possible to
- create a RAP with schema changes only?
- automatically (not manually) generate the SQL statements for a particular environment (either at the time of RAP creation or RAP import)?
 
I have not experimented yet, but I assume that the actual SQL depends on the target system.
This actually brings me to other questions:
Is the generated SQL independent of the actual DB flavour? (ANSI SQL?)
Does the generated SQL always contain all changes wrt. to a 'new' DB?
Can the generated SQL cope with variations in the target DB? (E.g. a table already exists or a property is already exposed)?
TIA,
Andreas

System Administration Installation and Deployment Data Integration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.