views:

67

answers:

2

Setting up a new database that has a comments table. I've been told to expect this table to get extremely large. I'm wondering if there is any particular reason why I wouldn't want to keep this table in the same database as the rest of the data for the site.

+3  A: 

Quantity of data will certainly affect performance in any RDBMS, however, there's no reason that this table should exist in a separate database on the same server. If the table truly will become very large with a lot of insert activity, then you might want to consider an ETL process that keeps an indexed copy for fast selection (mostly because indexes can negatively affect inserts despite the performance gain on selects)

Scott Anderson
+1 for the link to ETL. Now I have an official TLA for what I would have called, before today, my "gnarly performance hack".
Ben Dunlap
wouldn't that be a GPH? :)
Scott Anderson
+1  A: 

Keep the table in the same database for now, but it is well known that insert speed slows as the number of records increases.

There are some options to consider if the performance becomes unacceptable, for instance, if the data can be partitioned, split it across multiple tables in separate databases.

wsorenson