Document Storage

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

Does the number of documents scanned into the database have any effect on our functionality?  Is there any reason to limit the amount of information stored as .doc or .pdf in the research tab?

Bree Kneisler, Detroit Symphony Orchestra

Parents
  • Functionality, no.  Performance.... maybe (see bottom point which is unlikely).  Database (db) size increase yes:

    You won't gain or loose functionality by storing data here as as far as I'm aware, as you can't search the file name/contents from with the application.  Its easier find data about a specific person if its stored here though than stored on a flat file system people can alter manually.

    A document stored in the db is stored as a BLOB (easiest way of describing this is any file converted to text and the text stored in the database), but its just a record with a couple of reference ID.  The impact of this your db size will increase, but not any significant performance impact as its stored in its own table where the ID of that file is referenced by a one (?) of Tessitura screen.  Your DBA should be able to use the "Object Explorer Details" tab in Management Studio to see the current size of the documents table T_CUST_DOC.  

    It will have a performance impact if the actual binary data field is indexed and the reindexing process started during the day.  I have no idea why you'd want to do index a binary field, unless you were searching within the binary data (probably outside of the Tessitura application).  Ours, the document No and the customer No are the only fields indexed.

     

    Hope this helps

Reply
  • Functionality, no.  Performance.... maybe (see bottom point which is unlikely).  Database (db) size increase yes:

    You won't gain or loose functionality by storing data here as as far as I'm aware, as you can't search the file name/contents from with the application.  Its easier find data about a specific person if its stored here though than stored on a flat file system people can alter manually.

    A document stored in the db is stored as a BLOB (easiest way of describing this is any file converted to text and the text stored in the database), but its just a record with a couple of reference ID.  The impact of this your db size will increase, but not any significant performance impact as its stored in its own table where the ID of that file is referenced by a one (?) of Tessitura screen.  Your DBA should be able to use the "Object Explorer Details" tab in Management Studio to see the current size of the documents table T_CUST_DOC.  

    It will have a performance impact if the actual binary data field is indexed and the reindexing process started during the day.  I have no idea why you'd want to do index a binary field, unless you were searching within the binary data (probably outside of the Tessitura application).  Ours, the document No and the customer No are the only fields indexed.

     

    Hope this helps

Children
No Data