SQL Self Service

Eliminate wait times between teams. Make IT more productive.

SQL Self Service

SQL Self Service is a productivity tool of Clonetab which helps converting execution of SQL scripts to Self Service. Non-DBA IT Support teams (Business support, Development teams etc.) will be able to run their SQLs themselves on databases like Oracle, HANA, MySQL, MS-SQL, etc., through a Self-Service portal. Clonetab’s SQL Self Service (CTS3) tool drastically reduces the wait times on DBAs for SQLs execution through an approval workflow.

Workflow

  • Tightly integrated with Workflow for approvals and SQL execution. History of SQL execution maintained in the repository for compliance and future reference.

Role Based Access

  • control through Microsoft’s Active Directory (MSAD) integrated login. Allows access through MSAD groups. Inbuilt SODs- e.g. Requester can't be the approver

Email based approvals

  • allow approvers to approve from anywhere in the world (alternatively requests can be approved through CTS3 UI). Approvers can view the SQLs from the same emails before approving.

Download Results

  • The SQL execution results can be downloaded from the UI in PDF/CSV formats.

Blanket Approved Scripts

  • Users can have a set of pre-approved, re-usable SQL scripts where users can instantly run themselves without waiting for approval

Security

  • SSL enabled login, TLS support for the emails sent from the application

Schedulable tasks

  • SQL Executions can be scheduled. After approval, CTS3 engine will execute the SQLs as per the requested schedule.

Parallel Execution

  • SQLs can be executed in parallel based on the options selected by users.

Preview mode

  • Allows user to validate SQL before execution.

Why SQL Self Service

  • • A major portion of DBA tickets are SQL execution requests
  • • Frequent delays in execution of SQL requests due to other DBA priorities
  • • With manual SQL execution methods there is no audit trail, history, compliance

CTVault – Secure Password Vault

  • CTVault allows IT teams to store the passwords in a secure encrypted format and retrieve them when needed. Passwords can be a team’s password (public) or an individual’s password (private). The passwords are stored in Clonetab’s metadata repository in an encrypted format.
  • A password can be retried using Clonetab’s UI which appear as asterisks but can be copied to clipboard and used where needed.
  • 3 different types of passwords can be stored viz. application, database & Unix. They can be further segregated into Public & Private.