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