Database |
The database for which you want to submit the ticket. You must select a database on
which you have the change permissions.
|
Associated Iterations |
The iteration to be associated with the project. To select an iteration, click Select/Change Iteration. In the dialog box that appears, find the desired iteration and click Associate in the Actions column.
|
Reason Category |
The reason for the data change. This helps you find the ticket in subsequent operations.
|
Business Background |
The purposes or objectives of the change operation. This reduces unnecessary communication.
|
Execution Method |
The execution method of the ticket. Valid values:
- After Audit Approved, Order Submitter Execute
- After Audit Approved, Auto Execute
- Last Auditor Execute
|
SQL Statements for Change |
The SQL statements used for the change operation. DMS checks whether the syntax of
the SQL statements is valid when you submit the ticket. If the syntax is invalid,
you cannot submit the ticket.
|
SQL Statements for Rollback |
- Text: Enter the SQL statements used for rollback in the code editor.
- Attachment: Click Upload a file to upload the file that stores the SQL statements
used for rollback.
Note
- The file can be a TXT, ZIP, or SQL file and must not exceed 15 MB in size.
- The SQL statements that you specify for this parameter are used to roll back the change
operation.
|
Change Stakeholder |
The stakeholders involved in the change operation. All the specified stakeholders
can view the ticket details and participate in the approval process. Irrelevant users
except for DMS administrators and database administrators (DBAs) have no access to
the ticket details.
|
Attachments |
The file used as an attachment of the ticket to provide additional information about
the change.
|