The Cúram application and the Search Server application share a common database, but impose quite different demands on it. The SearchServiceRow table will see the bulk of writes and accesses, and it will grow very large, as it essentially contains a version of all the searchable data. The Cúram application will write to this table as searchable entities are inserted or updated. Periodically, if your Search Server is restarted or when it synchronizes, there will be a lot of reads from this table. It may make sense to place the SearchServiceRow table in a different tablespace to the rest of the application tables, depending on your organizations resources and needs.