We have implemented a close approximation of an OOBD in MSSQL 2005 for a department of ~100 staff in a larger financial institution.
While the volume of data will likely never be unmanageable, we are still looking ahead at possible future hurdles.
The db consists of 4 tables with limited number of sp. Indexing speaks to most issues when six of the seven fields form the composite key.
So the few 'plans' never change. Backup will be interesting because it may impact indexing. For this instance, could someone perhaps clarify the '20%'?
We could make the assumption that every 2 months we hit the 20% benchmark. What then, maintenance plans?