| Subject | Re: [ib-support] Cross-db query |
|---|---|
| Author | Svein Erling Tysvaer |
| Post date | 2002-10-30T08:27:07Z |
Hi Antonio!
Antonio wrote:
and in a previous post I found:
would be to put everything in the same database. My guess is that many of
the service dbs use the same table structure, but with different content -
that could be catered for using one table with views that restricted what
was to be visible at any point.
Generally I would say that there normally are three possibly good solutions
to problems like yours:
- Everything within the same database (simple, but could be impossible if
off-line access is required)
- Replication (more complicated)
- Export/Import of common data (if your "master" db doesn't have to be 100%
up-to-date all the time)
Woodys way of using master/detail is also interesting, but it does not
cater for your desire to use join directly.
I think this list can be a good help in discussing solutions to problems
like yours - and if people like heLen, Ann, Sean or Dmitry says "Don't do
that" you know you ought to at least consider a different solution ;o{ )
HTH,
Set
Antonio wrote:
>probably my implementation isn't sesible in Firebird, but I cannot findout any solution except that one I'm using. So if you have read my
>previous posts and if you know something about the design I describedbefore, please get me a Firebird compatible solution.
and in a previous post I found:
>the problem is that I need for this strange arrangement since I have sometables that are "common table" and some other that depends of
>kind of "service" that has to be managed. So I have only one "master" db,and many "Service" db, I don't know how many "Service" db I
>can have, but each "Service" db will have all the master tables plusother tables. Again, all the Sevice tables that refer to master, must
>contains the same data for all the Service dbs. I have already createdand tested an Delphi application that works on a Access database.
>Using the linked table, I'm able to obtain what I want, but since mydatabase going to be "too big", you know that access will become
>unuseful (performance very slow).Well, I don't know anything about your "Service" dbs, but my first thought
would be to put everything in the same database. My guess is that many of
the service dbs use the same table structure, but with different content -
that could be catered for using one table with views that restricted what
was to be visible at any point.
Generally I would say that there normally are three possibly good solutions
to problems like yours:
- Everything within the same database (simple, but could be impossible if
off-line access is required)
- Replication (more complicated)
- Export/Import of common data (if your "master" db doesn't have to be 100%
up-to-date all the time)
Woodys way of using master/detail is also interesting, but it does not
cater for your desire to use join directly.
I think this list can be a good help in discussing solutions to problems
like yours - and if people like heLen, Ann, Sean or Dmitry says "Don't do
that" you know you ought to at least consider a different solution ;o{ )
HTH,
Set