on 05-11-2007 7:10 PM
Hi all,
We already have an SRM system in production storing many large attachments on table BBPCONT.
We are facing huge performance problems because:
a) SRM holds the whole file content in memory during document upload.
b) During the process of saving the document, SRM creates one record in VBDATA table for each row that will be stored in BBPCONT. For large files, this process of inserting data at VBDATA takes a very long runtime.
I have two questions:
1) Anyone already handled this situation ?
2) We are thinking about using an external content server to store attachments. My concern is related to the attachments already stored at BBPCONT. Will these documents be available to the user or it is necessary to build conversion programs to move attachments from BBPCONT to the external server ?
Best Regards,
Roberto
Hello Roberto,
1) Yes, but we anticipated this performance issue by switching to an external Content Server. I also remember one performance issue: when you are uploading an attachement in your session, the system will store it in a temporary table BBP_TRANSCONTENT (the content is not stored in memory). It will be definitively stored in BBPCONT only if the user saves the purchasing document (otherwise we pollute the final table).
2) You have to "migrate" old documents from BBPCONT to the new Content Repository (ex:Content Server). There is a report for that : RSIRPIRL.
Rgds
Christophe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.