Is there better way to manage database deployment packages containing lots of lines?
We use one deployment workflow to handle all of our MSSQL or Oracle scripts. It works but we run into problems when users create packages with 30, 60, or 100 ore more lines. Each line executes one script. Some need to be run in specific order. When this happens, someone has to manually kick off each line one at a time in order. This takes a lot of time. Kick off line 1 and wait until it completes successfully.
Then kick off line 3..wait..
then maybe line 2..wait..
you get the point.
Lines are mostly out of order (or you have to skip cancelled lines) We have had issues in the past with PPM not running lines in sequential order if we grab all lines and click execute. (It might start with line 10, then start line 1, then line 4, etc) So if a package requires sequential deployment order, we do them manually.
Anyone else faced with this issue? How do you address executing in a specific order?
Also, has anyone come up with a better way to deploy all the users scripts without needing each on a separate pkg line?