Subject | RE: [ib-support] Non-technical database question |
---|---|
Author | Svein Erling Tysvaer |
Post date | 2003-02-24T13:20:41Z |
At 22:49 24.02.2003 +1000, you wrote:
tools who can make access Access databases. I don't think it is unusual to
have unhappy customers when changing from a desktop database to
client/server, but that is until they discover the benefits. E.g. with a
desktop database you normally browse entire tables even though you're only
interested in one or two records, whereas you in a client/server database
ask for a specific record or a limited set of records which you then show.
indexes this way can lead to it choosing to use wrong indexes. Result:
Possibly significant speed loss. I'd say it is the fault of the optimizer
and it may well be gone in Fb 1.5, but currently we all have to do our best
not to confuse it.
I think you've learned enough for a day by now, haven't you?
Set
>However I would be concerned if the use of a product such as firebird, overWell, some things may appear to be slower and there are more third-party
>say Access produced negative results.
tools who can make access Access databases. I don't think it is unusual to
have unhappy customers when changing from a desktop database to
client/server, but that is until they discover the benefits. E.g. with a
desktop database you normally browse entire tables even though you're only
interested in one or two records, whereas you in a client/server database
ask for a specific record or a limited set of records which you then show.
> >I took a quick look and my only comment is that you must remove thoseMaybe I wasn't precise enough. Confusing the optimizer by duplicating
> >indexes that are duplicates of keys (primary or foreign) - it only confuses
> >the optimizer to have duplicate indexes. You may keep the descending ones,
> >keys just create ascending indexes (I think).
>*L*, I am slightly confused, but am going to take a look at my keys, and see
>what you mean. your thoughts are appreciated.
indexes this way can lead to it choosing to use wrong indexes. Result:
Possibly significant speed loss. I'd say it is the fault of the optimizer
and it may well be gone in Fb 1.5, but currently we all have to do our best
not to confuse it.
I think you've learned enough for a day by now, haven't you?
Set