|
Go
![]() |
New
![]() |
Find
![]() |
Notify
![]() |
Tools
![]() |
Reply
![]() |
|
I am a sysadmin who recently joined the company with this application. I noticed that the SQL server had 120 databases. When I queried the junior admin responsible for maintaining the app, he told me that an SQL database is created for every new textbase that is created. Is this true? If so, why does a SQL database have to be created for every textbase.
Can someone point me to a document that explains the technical details of when a textbase is created and how the SQL database comes into play. I am trying to get a better understanding of the process. Thanks in advance. |
|||
|
Best to read the "Content Server Admin Guide" doc that comes with the Content Server software. It will at least give you a background to the questions you're asking. You can find the latest at http://support.inmagic.com/web/.
As to why a SQL db is created for every new textbase... um. Good question, and no one outside of Inmagic could have a definitive answer. I suppose they were used to thinking of textbases as discrete units when they adapted the DB/Textworks software to Sql Server. It's not something you can do anything about. Peter Tyrrell, MLIS Director and Lead Developer Andornot Consulting Inc. http://andornot.com/about/developerblog http://twitter.com/andornot |
||||
|
thanks for the info. I just have never seen an application create this many databases. My problem is that there is going to be a app upgrade, and they want to use one of the other production servers, because the other server was slow in processing. But I am wary of allowing an app that creates so many databases on one of the other production servers.
Well, I guess that I will have to do a lot more reading. |
||||
|
Textbases resemble databases more than tables. They can have different owners or departments, may be completely unrelated in terms of mission or purpose, and are often backed up and/or managed individually. They also have fields that can contain multiple entries, and this is accommodated using tables within the SQL database. Other tables enable the specialized field-specific filing rules supported by the product. Most Inmagic customers have far fewer than 120 textbases unless they are segmenting a collection for some reason, perhaps by year.
Lisa Weiss | QA Team Leader | Inmagic, Inc. 200 Unicorn Park Drive, 4th Floor | Woburn, MA 01801 Tel: 781.938.4444 | Fax: 781.938.4446 lweiss@inmagic.com | www.Inmagic.com |
||||
|
| Powered by Eve Community |
| Please Wait. Your request is being processed... |
|

