we have a huge db ( > 50GB, about 45K docs), very painful to work with. it seems the only way is to split the db into 2 (or 3) dbs. BUT users really need to access 2 dbs constently, we are looking for a way to have 1 screen to view documents from 2 different dbs. Our ultimate goal is to keep usage as simple as possible for users (lawyers, auditors,…)
anybody has this kind of issue?
domain search is the only way to resolve our problem?
You mention lawyers, auditors, etc. Do both (multiple?) groups need access to all documents at the same time? Will the lawyers ever need to look at the documents that the auditors will be looking at? If not, why not split the databases up along functional lines?
we have a huge db ( > 50GB, about 45K docs), very painful to work with. it seems the only way is
to split the db into 2 (or 3) dbs. BUT users really need to access 2 dbs constently, we are
looking for a way to have 1 screen to view documents from 2 different dbs.
does that mean
A. You have one db that is becoming unmanageable or unusable in some sense
or
B. Your users have two databases they need to work with all the time, and one of these is becoming unusable
I think you mean (A).
Fifty G is quite a lot; 45k documents is not.
I suspect you just have a badly-designed application that needs (1) some refactoring and (2) maybe some offloading of attachments. Splitting it up is only a good idea if splitting it up actually addresses the problem, and I don’t think you have defined the problem clearly enough.
First, come up with a crystal-clear statement of the problem, like “The application takes two minutes to open when thrity seconds is the maximum acceptable”, or “Form X takes forty-five seconds to save and fifty-two seconds to open”, or “there are too many views in the interface, making it confusing to find what we want.”
You could have a third database that only contains “light” documents with the basic info for searching and categorizing and links to the original documents.And every time anyone creates new documents in any of the main databases a light document is created in this third db
Do you know how much of the 50Gb is taken up with view indexes? You can check this from the admin client, right click the database from the files tab and click manage views. What makes each doc so big???
If it’s views taking up the space I would look and deleting as many as possible that aren’t used, combining them where possible and designing them better. ie. remove sortable columns if not needed, don’t have calculations is selection formulas etc