This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:servers [2011/03/28 22:06] deb |
integration:rdbms:servers [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| [[integration:rdbms:queries|Queries]] | | [[integration:rdbms:queries|Queries]] | | ||
| [[integration:rdbms:updates|Updates]] | | [[integration:rdbms:updates|Updates]] | | ||
| - | [[integration:rdbms:implementation|Implementation Guides]] | + | [[integration:rdbms:integration|Integration Guides]] |
| Line 20: | Line 20: | ||
| Typically, Omnidex is placed on an Omnidex Server and the relational database is placed on a Relational Database Server. This allows each to utilize system resources as they need without interference from the other. | Typically, Omnidex is placed on an Omnidex Server and the relational database is placed on a Relational Database Server. This allows each to utilize system resources as they need without interference from the other. | ||
| - | Applications can be written to direct all query traffic to Omnidex, or the application can split the traffic between Omnidex and the relational database. Applications that direct all query traffic to Omnidex simple switch the connections from the relational database to Omnidex. Applications that will split the traffic maintain concurrent connections to Omnidex and the relational database. | + | Applications can be written to direct all query traffic to Omnidex, or the application can split the traffic between Omnidex and the relational database. Applications that direct all query traffic to Omnidex simply switch the connections from the relational database to Omnidex. Applications that will split the traffic maintain concurrent connections to Omnidex and the relational database. |
| {{:integration:rdbms:rdbms_server_architecture.png|}} | {{:integration:rdbms:rdbms_server_architecture.png|}} | ||