You are viewing limited content. For full access, please sign in.

Question

Question

New repository impact re database creation

asked on January 30, 2015

As I understand it, each new repository on a Laserfiche server results in a new database for that repository.
Does running audits on the new repository likewise require a separate audit database or does the existing one work centrally? Does one workflow database also serve all repositories or does each repository require its own workflow database? Lastly, is there any performance guidance on how many repository databases can coexist on one server?

0 0

Answer

SELECTED ANSWER
replied on January 30, 2015

Each repository has its own database. The same goes for Audit Trail (each repository you set up in the reporter creates a corresponding SQL database). One single SQL database serves one installation of Workflow, regardless of how many repositories are used in Workflow on that server.

The number of database that can live on the same server depends on the server specs and the load on each one. Microsoft might be a better source of documentation on that.

As a very basic rule, Audit Trail is very SQL-intensive if you run reports a lot. We usually recommend putting it on its own SQL instance so it does not affect the performance of Laserfiche. Depending on how much data you plan on keeping around for reports, that separate instance could run on SQL Express.

1 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.