System Tables
System tables are included out-of-the-box with your Cinchy platform, and can be used to track and manage a variety of data.
List System Tables
You can query for a list of your system tables using the below:
SELECT [Name]
FROM [Cinchy].[Tables]
WHERE [Deleted] IS NULL
AND [Domain] = 'Cinchy'
Visible Tables
Some table are not visible in the homepage or via a homepage search, however they can still be queried for data provided you have the correct entitlements.
For example, the [Cinchy].[Table Access Control] table is not visible, but if if you wanted to view the Access Controls of the [HR].[Employees] table you could do so as follows:
SELECT *
FROM [Cinchy].[Table Access Control]
WHERE [Deleted] IS NULL AND [Table]='HR.Employees'
Default System Tables
| Name | Description |
|---|---|
| Users | This table manages user authentication and profile data. Cross-department collaboration enhances security, user management, and personalized service delivery. |
| System Colours | This table is dedicated to maintaining colours. |
| System Icons | This table is dedicated to maintaining colours. |
| Domains | This table is dedicated to maintaining domains. |
| Tables | This table is dedicated to maintaining table definitions. |
| Table Columns | This table is dedicated to maintaining column definitions. |
| Groups | This table is dedicated to maintaining user groups. |
| Table Access Control | This table is dedicated to maintaining table access control. |
| Models | This table is dedicated to maintaining models. |
| Views | This table is dedicated to maintaining views. |
| View Columns | This table is dedicated to maintaining the list of columns associated with a view. |
| View Column Link Graph | This table is dedicated to maintaining the series of links to traverse when referencing columns that belong to a different table in a view. |
| Applets | This table is dedicated to maintaining applets. |
| Saved Queries | This table is dedicated to managing user saved queries that can be exposed via the REST API. |
| Launcher Objects | This table is dedicated to managing user specific launcher objects. |
| User Login Attempts | This table is dedicated to tracking user login activity. |
| User Password History | This table is dedicated to tracking previous user passwords. |
| Data Security Classifications | This table is dedicated to maintaining data security classifications. |
| User Defined Functions | This table is dedicated to managing user defined functions. |
| Integrated Clients | This table is dedicated to maintaining integrated clients. |
| System Properties | This table is dedicated to managing system properties. |
| Data Experience Definitions | This table is dedicated to managing data experience definitions. |
| Formatting Rules | This table is dedicated to managing formatting rules. |
| Comments | This table is dedicated to maintaining comments. |
| Data Sync Configurations | This table is dedicated to managing data sync configurations. See cli.docs.cinchy.com on how to synchronize data with Cinchy. |
| Execution Log | This table is dedicated to tracking execution logs of data syncs. |
| Execution Errors | This table is dedicated to tracking execution errors of data syncs. |
| Networks | This table is dedicated to managing custom data networks. |
| Languages | This table is dedicated to maintaining languages. |
| Regions | This table is dedicated to maintaining regions. |
| Literal Groups | This table is dedicated to maintaining literal groups. |
| Literals | This table is dedicated to maintaining literals. |
| Literal Translations | This table is dedicated to maintaining literal translations. |
| User Preferences | This table is dedicated to maintaining user preferences. |
| Data Experience Reference Data | This table is dedicated to managing reference data for data experiences. |
| Data Experience Releases | This table is dedicated to maintaining data experience releases. |
| Data Experience Release Artifacts | This table is dedicated to maintaining data experience release artifacts. |
| Listener Config | The table manages event listener configurations. Enabling cross-department data collaboration ensures synchronized event handling, improving operational efficiency. |
| Event Log | This table is dedicated to logging events. |
| Forbidden Passwords | A user will not be able to change their password to any of the strings in this table. |
| User Grants | This table is dedicated to maintaining user grants, such as, reference and refresh tokens as well as authorization codes and consents. |
| Files | This table is dedicated to maintaining files. |
| Webhooks | The table manages webhook configurations. Cross-department collaboration on this data ensures seamless integration and automation across various systems. |
| Server Types | server types. |
| Splinter | Server configuration data. |
| Event Listener State | The table manages event listener states and configurations. Cross-department collaboration ensures synchronized event handling and efficient system operations. |
| Personal Access Tokens | This table manages personal access tokens and their sharing details. Cross-department collaboration enhances security and access management efficiency. |
| External Secrets Manager | This table manages external secrets (credentials, keys). Cross-department collaboration ensures secure, consistent access control and reduces redundancy. |
| Secrets | The table manages sensitive information ("Secrets") including sources, identifiers, values, and access groups. Cross-department collaboration enhances security and efficiency. |
| Durations | The table manages durations for scheduling tasks. Enabling cross-department data collaboration on this data improves task planning and resource allocation efficiency. |
| Schedules | This table manages schedules for the Cinchy Scheduler. Enabling cross-department data collaboration on this data improves scheduling efficiency and coordination. |
| Automation Packages | The Automation Packages table serves as a central repository for managing information related to various automation packages. It is designed to store essential details such as the name of the package, groups with read/write access, and recipients designated to receive notifications. |
| Automations | The purpose of the Automations table is to provide a comprehensive repository for storing and managing information about individual automations. Key details such as the automation's name, the associated package, schedule, and Service Level Agreement (SLA) are captured in this table. The Concurrency Policy column manages concurrent execution, optimizing resource utilization. |
| Automation Steps | Designed to define the sequence and actions within automations, the Automation Steps table orchestrates the execution flow. It captures crucial information like the sequence and description of steps, along with specifications for running steps based on predefined conditions. |
| Automation Execution History | The Automation Execution History table serves as a historical record keeper, tracking the execution details and status of each automation. Key information, including the status, trigger time (in Coordinated Universal Time - UTC), and total execution time, is stored for analysis and audit purposes. This table enables users to gain insights into the performance and outcomes of past automation runs, facilitating informed decision-making and troubleshooting. |
| Automation Steps Execution History | Complementing the Automation Execution History, the Automation Steps Execution History table provides a granular view of individual steps within automation runs. It records details such as the status, trigger time (UTC), and execution time for each step. This table is instrumental in understanding the intricacies of step-wise execution, identifying potential bottlenecks, and assessing the overall efficiency of automation processes. |
| User Defined Topics | Topics to be used by Listener Configs. |