All Products
Search

This Product

    Data Management:Programmable objects

    Document Center

    Data Management:Programmable objects

    Last Updated:Mar 30, 2026

    Data Management (DMS) lets you change stored procedures and stored functions through a managed ticket workflow — with syntax validation, database administrator (DBA) approval, and an audit trail built into every change.

    When to use this feature

    Use this feature when you need to modify an existing stored procedure or stored function through a governed change process.

    Prerequisites

    Before you begin, ensure that you have:

    • A supported database registered in DMS with change permissions granted to your account

    • The stored routine SQL ready to deploy

    Supported database engines:

    • MySQL: ApsaraDB RDS for MySQL, PolarDB for MySQL, MyBase for MySQL, and third-party MySQL databases

    • SQL Server: ApsaraDB RDS for SQL Server, MyBase for SQL Server, and third-party SQL Server databases

    • PostgreSQL: ApsaraDB RDS for PostgreSQL, PolarDB for PostgreSQL, MyBase for PostgreSQL, AnalyticDB for PostgreSQL, and third-party PostgreSQL databases

    • MariaDB: ApsaraDB for MariaDB and third-party MariaDB databases

    • PolarDB for PostgreSQL (Compatible with Oracle)

    Limitations

    • Only stored procedures and stored functions can be changed through this feature. Other programmable object types are not supported.

    • DMS validates the syntax of your SQL statements but does not check business logic. Verify that your stored routine logic meets your requirements before submitting.

    • Stored routines used for this type of change cannot include transaction characteristic specifications.

    • You cannot back up the database using a snapshot image before running a stored routine change.

    How it works

    A stored routine change goes through four stages:

    1. Submit — Fill in the ticket parameters and pass DMS syntax validation.

    2. Precheck — DMS validates key elements of your ticket settings.

    3. Approve — The ticket is reviewed by a DBA based on your organization's approval rules.

    4. Execute — Run the change immediately or on a schedule, then review the operation logs.

    Submit a stored routine change ticket

    1. Log on to the DMS console V5.0.

    2. In the top navigation bar, choose Database Development > Data Change > Programmable Object Permissions.

      If you use the DMS console in simple mode, move the pointer over the 2023-01-28_15-57-17.png icon in the upper-left corner and choose All Features > Database Development > Data Change > Programmable Object Permissions.

    3. On the Data Change Tickets page, fill in the ticket parameters in the Apply step.

      Parameter Description
      Database The database to change. Select a database for which your account has change permissions.
      Execution method When and by whom the change runs after approval. Options: After Audit Approved, Order Submitter Execute; After Audit Approved, Auto Execute; Last Auditor Execute
      SQL statements for change The SQL statements for the change. DMS checks syntax when you submit — invalid syntax blocks submission.
      SQL statements for rollback The rollback SQL statements. Enter them in the code editor (Text) or upload a file (Attachment). Supported file types: TXT, ZIP, or SQL, up to 15 MB.
      Change stakeholder Users who can view the ticket and participate in approval. Users not listed here — except DMS administrators and DBAs — cannot access the ticket details.
      Attachments (Optional) Supporting files that provide additional context for the change.

    4. Click Submit. DMS runs a precheck on your ticket settings. If the precheck fails, modify the ticket as prompted and resubmit. Repeat until the ticket passes.

    5. After the precheck passes, click Submit for Approval.

      Review your settings and schedule before submitting for approval — you cannot modify them afterward. By default, data change tickets are reviewed by DBAs. For details on approval rules, see SQL Correct.

    6. After the ticket is approved, click Execute Change. In the Task Settings dialog box, set the Execution Strategy:

      • Running immediately: The task runs as soon as you click Confirm Execution.

      • Schedule: Specify a future start time.

    7. After the task completes, click Details to review the operation logs, including SQL statements, execution duration, and scheduling details.

    What's next

    • SQL Correct — Learn how DMS approval rules are configured and how to customize them for your team.