Re: systabauth fragmentation

Jonathan Leffler writes: |> >In one of my databases the systabauth table is fragmented into 10 |> >segments. What's the best way to fix a system table when this happens. |> >I usually unload the table, recreate it and reload. But, I'm afraid |> >to try anything like this with a system table. |> |> (1) It probably doesn't matter. That is to say, the 8 extent limit makes a |> marginal difference to performance, but the difference is going to be |> small bits of a tenth of a percent. |> |> (2) You can set next extent size on a system table: |> ALTER TABLE Systabauth MODIFY NEXT SIZE 64; |> |> (3) You won't be able to rebuild any system table short of dropping the |> database and rebuilding it. Not necessarily. I have found that tbunloading a table then tbloading it back it will cause the extents to be compressed into a single extent. I haven't tested this exhaustively, so I can't state unequivocably that it will work in every situation. But tbunloading the database may well have that effect on each component table. Dave Disclaimer: These opinions are not those of Informix Software, Inc. ************************************************************************** "I look back with some satisfaction on what an idiot I was when I was 25, but when I do that, I'm assuming I'm no longer an idiot." - Andy Rooney