GLOSSARY ENTRY (DERIVED FROM QUESTION BELOW) | ||||||
---|---|---|---|---|---|---|
|
18:26 Aug 31, 2008 |
German to English translations [PRO] Tech/Engineering - Telecom(munications) / BlackBerry sync | |||||||
---|---|---|---|---|---|---|---|
|
| ||||||
| Selected response from: Ken Cox Local time: 21:48 | ||||||
Grading comment
|
Summary of answers provided | ||||
---|---|---|---|---|
3 +3 | master system |
| ||
5 | the leading system |
|
the leading system Explanation: Sounds like the source text is talking about Microsoft Exchange. |
| |
Login to enter a peer comment (or grade) |
master system Explanation: One option, although it is apparently used most often in multi-system database system applications and patent documents. There may be another term that is more appropriate to this particular context (and audience). A master/slave relationship is a very common concept in IT. In a master/slave relationship, the master system is in control and dictates what the slave does, and it is usually the only system that is allowed to (formally) initiate transactions. The situation here probably does not go as far as a full, formal master/slave relationship. I understand it as meaning which system is regarded as the source of current master data used to update the other system so that they are synchronised (which effectively that means they hold the same data). It may also be the system that initiates and controls the transactions. sample ref: Data Synchronization How does the ParAccel database have the data necessary to satisfy the queries it intercepts, you ask? Triggers in the master database, at present. (Log shipping coming in the future.) The triggers record changes in an audit table, and the ParAccel system periodically polls for the master system for those records. This means, of course, that there's an inherent delay between when data in the master system changes and when it is available in the ParAccel system. The polling interval is configurable though, so you can control this delay. Setting it lower than a couple seconds will probably create overhead problems though, so I question whether up-to-the-second synchronization is really feasible. While I seriously doubt that this delay would be an issue for most systems it's something that must be considered nonetheless. www.fulltablescan.com/index.php?/categories/12-ParAccel -------------------------------------------------- Note added at 2 hrs (2008-08-31 20:55:39 GMT) -------------------------------------------------- erratum: *which effectively means that they hold...* |
| |
Grading comment
| ||