Or, if they *have* to be accurate, then how about an actual table that is updated through triggers on the target tables? In other words, if you are interested in the count of Table1, then create a trigger on Table1 for inserts and deletes that modifies the record in your new TableRecordCount table for Table1 by either incrementing or decrementing it by the proper amount. This will, of course, slow the inserts and updates slightly, but you need to weigh that against the cost of calculating the total every time you need it. Of course, you may want to start by checking the plan of your SELECT COUNT statements currently to verify that they are not doing tablescans. Here is a thread that discusses that:

[url]http://www.dbasupport.com/forums/showthread.php?threadid=6617[/url]

HTH,

- Chris