I have a B2B web site that supports both online transactional processing as well as reporting requests. This is not what one would consider a high volume site but we do have about 100 active users per day. About 10% of the data is active and undergoing daily updates while 90% of the transactions are completed and no longer being modified. So the site supports transactions on the 10% data and allows users to review their total activity (static past and active present). What types of database design / schemas would best support this dual purpose database? At this time, it's a single relational database but it is growing larger and could perhaps warrant a separation into an active oltp database with replication or other duplication to a separate reporting database. Are there other options? Thanks in Advance.