Supporting Finite Element Analysis with a Relational Database Backend, Part II: Database Design and Access
| dc.creator | Heber, Gerd | |
| dc.creator | Gray, Jim | |
| dc.date | 2007-01-25 | |
| dc.date.accessioned | 2026-07-07T07:43:13Z | |
| dc.date.available | 2026-07-07T07:43:13Z | |
| dc.description | This is Part II of a three article series on using databases for Finite Element Analysis (FEA). It discusses (1) db design, (2) data loading, (3) typical use cases during grid building, (4) typical use cases during simulation (get and put), (5) typical use cases during analysis (also done in Part III) and some performance measures of these cases. It argues that using a database is simpler to implement than custom data schemas, has better performance because it can use data parallelism, and better supports FEA modularity and tool evolution because database schema evolution, data independence, and self-defining data. | |
| dc.identifier | https://arxiv.org/abs/cs/0701160 | |
| dc.identifier | http://arxiv.org/abs/cs/0701160 | |
| dc.identifier.uri | http://salesiana.dossiersoluciones.com/handle/123456789/122740 | |
| dc.subject | Databases | |
| dc.subject | Computational Engineering, Finance, and Science | |
| dc.title | Supporting Finite Element Analysis with a Relational Database Backend, Part II: Database Design and Access | |
| dc.type | text |