For best performance, the transaction log should be on a separate disk.
Does the writing of the log benefit from a battery backed controller as well?
If not, what do people think about writing the transaction log to a flash card
or the like?
We are reindexing frequently, and I'm wondering if
this is really necessary, given that it appears to
take an exclusive lock on the table.
Our table in question is vacuumed every 4 minutes, and
we are reindexing after each one.
I'm not a fan of locking this table that frequently,
even if it is
I have a table that is purged by 25% each night. I'd like to do a
vacuum nightly after the purge to reclaim the space, but I think I'll
still need to do a vacuum full weekly.
Would there be any benefit to doing a cluster instead of the vacuum?
---(end of
We have a highly active table that has virtually all
entries updated every 5 minutes. Typical size of the
table is 50,000 entries, and entries have grown fat.
We are currently vaccuming hourly, and towards the end
of the hour we are seeing degradation, when compared
to the top of the hour.
