Thomas Steinmaurer skriver:

> A golden rule for the index depth is/was not greater 3, but I guess this
> was ages ago, but with the current machine power even in desktop PCs,
> I'm not sure if this rule still applies or even if the index tree depth
> matters anyway.

OK.

> Don't know if you have mentioned your used page size somewhere, but I
> would go with 8K. Increasing the page size *might* also lead to a more
> flatten index tree, but a depth of 4 might be still possible. 16K is the
> maximum page size.

It's 4k currently. We did bump it up to 8k once before, but apparently
neglected to choose other than default at some point when we recreated
the DB. I don't know why we chose 8k before, but it was nothing to do
with index depth.

> Changing the page size on an existing database is done by running a
> backup/restore cycle, providing the new page size at restore time. But
> you probably know that.

Yes. But it will take about a day to do it.

> I also think that using non-Ansi characters in object names isn't a good
> idea for the long-term. There might be tools out there, which have
> problems with that.

Well, I did agree once, but these days I think tools should support
everything that the DB itself supports, so if I stumble upon a tool that
can't handle it, I'm going to report it as a bug and require a fix.
Failing that, I'll choose a better tool or write it myself. The OO
framework ECO does work fine with it, as does FlameRobin. Those are
really the only tools I use at this time. Also, the OO framework does
support schema evolution, so shouldn't be too hard to rename the stuff
should it be required later.

Regards,
Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64