We don’t have that information available directly in information_schema. You can approximate it in some cases based on this:
One of the system views in SingleStore that contains metadata is MV_COLUMNAR_SEGMENT_INDEX which includes a CREATION_TIME column, but this pertains to columnstore segments and not to the database as a whole.
In SingleStore (formerly known as MemSQL), you can gather information about database creation date, table creation date, and user actions using various SQL queries and system views. Here’s how you can obtain this information:
Database Creation Date:
You can find the creation date of a database by querying the information_schema.DATABASES system view. Here’s the SQL query:
SELECT database_name, create_time
FROM information_schema.DATABASES
WHERE database_name = 'your_database_name';
User who created the Database:
SingleStore does not directly track the user who created a database. However, if you maintain an audit trail or logging system, you may be able to retrieve this information from your logs.
Table Creation Date:
Table creation date information can be obtained from the information_schema.TABLES system view. Here’s the SQL query:
SELECT table_name, create_time
FROM information_schema.TABLES
WHERE database_name = 'your_database_name';
Commands run on a particular Database:
SingleStore does not store a history of executed commands by default. However, you can set up auditing or logging mechanisms to track commands executed against the database. Additionally, if you’re using the SingleStore Studio GUI, you can view the history of executed queries within the Studio interface.
Please note that while SingleStore provides system views to gather information about database objects, user actions, and more, it may not cover every specific requirement you have. You may need to supplement this information with external logging or auditing mechanisms depending on your use case and requirements.