Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The SQL code file will be attached to the Jira.
  • The SQL code file will contain a decription of the script's intended purpose and specific actions as well as the Jira number. This is to be located at the top of the script.
  • The SQL script will be checked into subversion.
  • Like any other development object, the script will folow the above described SDLC process. A script will not be deployed to PRD until user signoff has been secured.
  • Execution of the script in PRD will occur one of two ways:
    • If the script is part of a larger development request, it will be executed by the CM following the successful build of the environment.
    • Today: If the script is a one-time requirement for the purpose of resolving a data issue, a request will be submitted to the DBAs to execute the script in production at a time when all users are off the system or when deemed appropriate by Finance Systems.
    • In Process: If the script is a one-time requirement for the purpose of resolving a data issue, an ad-hoc job request will be submitted to Scheduling to execute (from Control-M command line) the shell script in KFS, passing the name of the SQL script file as a parameter.

    • The resulting actions of the script in PRD must be validated by the requestor prior to resolving the Jira.

...