Jason,

> What are the dimensions of the unique key columns? If they are sizable

then

> I strongly discourage you using them in the KeyLinks property. If they are
> large they get duplicated and use up more memory than otherwise. Keys and
> data are buffered separately with IBO.
>
> Is there a reason you cannot just use an integer surrogate key column?

I had a brief discussion on this topic with Helen and am really interested
in implementing a surrogate key but cannot figure out how to make it work
with the current structure of the database. From a unique key standpoint, my
database is basically laid out as follows:

15% of the master tables have a unique key of CO, PARCEL
35% of the master tables have a unique key of CO, YR, PARCEL
25% of the master tables have a unique key of CO, YR, PARCEL, DWELLING
25% of the master tables have a unique key of CO, YR, PARCEL, STRUCTURE
I also have about 100 code tables used to drive calculations with a unique
key of either CO, CODE or CO, YR, CODE.

At login, the user selects a community and year (CO, YR) to work with
parcel, dwelling and building structure related information.

Using a surrogate key would certainly cut down on the size of the database
and most like cause the optimizer to behave much better, so that I would not
have to constantly hard code in a plan.

Could you or someone on this list, PLEASE explain how I would go about
creating surrogate keys in this situation ? Any brief examples would be a
great help.

Thanks,

Chris Landowski
Dynamic Software Solutions