|
We have multiple clients that are in, what we call, a three-tiered replicating environment. This means we have a Main Site that has Remote Sites. Once those Remote Sites are loaded, we create sites in those and extract them. So the main site never really 'knows' about the third level of remote sites. My question is, will there be a problem with using Global Autoincrements in this type of replicating environment? EDIT: Thanks, |
Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 29 Jan '10, 16:58
question was seen: 2,396 times
last updated: 30 Jan '10, 08:42
How do you generate the GLOBAL DATABASE ID currently for the regular remotes, i.e. the remotes of the main site? - I guess that will tell whether the additional layer will fit smoothly or must be regarded carefully.
We implemented remote sites before these options were available and as such, its a complete custom setup that uses our own db tables to hold key ranges, plus flat files at each site that indicates what its id value is.
Well, then the question is whether you custom GLOBAL DATABASE ID (or similar) management is able to guarantee the uniqueness. -- We have used a different kind of three tier setup, namely MS SQL <-> MobiLink <-> ASA main db <-> SQL Remote <-> ASA remotes. In that setup, we used GLOBAL DATABASE IDs on the ASA side and made sure that all MS SQL generated PKs were below a certain barrier (i.e. we reserved something like a ID space for the MS-SQL database). That worked well.
My thoughts were to still use a table in our database, but instead of having ranges for every single table, it would have ranges for database ids, and then I would use the sp_hook_dbxtract_begin to set the global_database_id to the next value in the range for that site.