visual3d:documentation:definitions:file_formats:sql_database_definition
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| visual3d:documentation:definitions:file_formats:sql_database_definition [2024/06/17 18:15] – created sgranger | visual3d:documentation:definitions:file_formats:sql_database_definition [2024/07/17 15:45] (current) – created sgranger | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | + | ====== SQL Database Definition ====== | |
| - | + | ||
| The exporting of data from Visual3D requires an external database with a predefined data structure. | The exporting of data from Visual3D requires an external database with a predefined data structure. | ||
| Line 18: | Line 16: | ||
| \\ | \\ | ||
| - | [[Exporting_Data_to_a_Relational_Database_doc_27915504.jpg]] | + | {{:Exporting_Data_to_a_Relational_Database_doc_27915504.jpg}} |
| \\ | \\ | ||
| - | ==== Table Structure Definition | + | === Table Structure Definition === |
| The actual SQL database tables loosely follow the Visual3D data tree layout, and are defined below: | The actual SQL database tables loosely follow the Visual3D data tree layout, and are defined below: | ||
| Line 43: | Line 41: | ||
| - | ==== Parsing Raw Data ==== | + | === Parsing Raw Data === |
| The data exported from Visual3D into a database is too complex and dynamic for a rapid database transfer. The overhead associated with SQL Insert commands is quite high, even with optimization. For that reason, the data is formatted into a delimited structure to make intelligent post-process parsing possible. For each signal, a database row is created consisting of the signal identifier (i.e. foreign key) and a big string of raw data. The raw data - whether target data per frame, analog data, or calculated metrics – is retrieved and parsed into the following structure. | The data exported from Visual3D into a database is too complex and dynamic for a rapid database transfer. The overhead associated with SQL Insert commands is quite high, even with optimization. For that reason, the data is formatted into a delimited structure to make intelligent post-process parsing possible. For each signal, a database row is created consisting of the signal identifier (i.e. foreign key) and a big string of raw data. The raw data - whether target data per frame, analog data, or calculated metrics – is retrieved and parsed into the following structure. | ||
| Line 53: | Line 51: | ||
| - | ==== Signal Example | + | === Signal Example === |
| For a target signal called “LANK” we would see a row in the database for the signal name in L4_name table with a system generated ID called dnameID and a dataname. For example: 849 “LANK” | For a target signal called “LANK” we would see a row in the database for the signal name in L4_name table with a system generated ID called dnameID and a dataname. For example: 849 “LANK” | ||
| Line 124: | Line 122: | ||
| \\ | \\ | ||
| However, pivot tables can be avoided if only certain information, | However, pivot tables can be avoided if only certain information, | ||
| - | |||
| - | |||
visual3d/documentation/definitions/file_formats/sql_database_definition.1718648137.txt.gz · Last modified: 2024/06/17 18:15 by sgranger