visual3d:documentation:definitions:file_formats:sql_database_definition
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| visual3d:documentation:definitions:file_formats:sql_database_definition [2025/07/17 19:39] – sgranger | visual3d:documentation:definitions:file_formats:sql_database_definition [2025/09/12 19:04] (current) – [SQL Database Definition] wikisysop | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| The exporting of data from Visual3D requires an external database with a predefined data structure. There are no restrictions as to which database system is used since connection to it is provided by ODBC connections. HAS-Motion’s sample code is provided using Visual Basic for Application in Microsoft’s Access database system. The data structure is normalized to eliminate redundant data entry. The specific data values for signals, metrics, and analog data, however, are stored in a large single string that must be parsed prior to using the data for analysis purposes. This approach was necessary due to the inherent speed limitations a relational database has with storing tremendous amounts of data. Note that some RDBMS systems may need add-on modules or extensions to support Transforms or Pivot Table capabilities. \\ | The exporting of data from Visual3D requires an external database with a predefined data structure. There are no restrictions as to which database system is used since connection to it is provided by ODBC connections. HAS-Motion’s sample code is provided using Visual Basic for Application in Microsoft’s Access database system. The data structure is normalized to eliminate redundant data entry. The specific data values for signals, metrics, and analog data, however, are stored in a large single string that must be parsed prior to using the data for analysis purposes. This approach was necessary due to the inherent speed limitations a relational database has with storing tremendous amounts of data. Note that some RDBMS systems may need add-on modules or extensions to support Transforms or Pivot Table capabilities. \\ | ||
| \\ | \\ | ||
| - | MS Access has the functionality built-in, so some example code provided by C-Motion may not transfer directly to other systems.) The picture below illustrates the how the Visual3D signal and event tree structure maps to database tables. The Patient Info table is provided as a sample illustration on where the relationship to patient information may be managed. The BLOB table is where the raw data is stored after the exporting process is done, and a Raw Data table is provided for the parsed results. Sample database definitions and sample routines for parsing and managing data are provided by C-Motion. \\ | + | MS Access has the functionality built-in, so some example code provided by C-Motion may not transfer directly to other systems.) The picture below illustrates the how the Visual3D signal and event tree structure maps to database tables. The Patient Info table is provided as a sample illustration on where the relationship to patient information may be managed. The BLOB table is where the raw data is stored after the exporting process is done, and a Raw Data table is provided for the parsed results. Sample database definitions and sample routines for parsing and managing data are provided by HAS-Motion. \\ |
| {{: | {{: | ||
visual3d/documentation/definitions/file_formats/sql_database_definition.1752781170.txt.gz · Last modified: 2025/07/17 19:39 by sgranger