InfoPath Dev

I'm looking for some guidance on ways to help reduce the size of the DBXL database.  We have several document types we submit with images and also have some which submit to a separate SQL database, and / or to SharePoint.  In the case where we submit to SharePoint and SQL, we have three copies of the data (one in DBXL, one in our SQL database, and one in SharePoint), and two copies of the images (one in DBXL, and one in SharePoint).

I'm curious if there is a way to reduce database size with any search or history flags (I've seen that setting "EnableFullTextSearch" to "false" can help in other forum posts).

I'm also wondering if there is a way to disconnect the association for older documents between the DBXL web service and the associated data in SharePoint or SQL.  Ideally, at some point we could delete the documents in DBXL and NOT have that delete the associated SQL or SharePoint data for the purposes of archiving.

Lastly, with images on forms, I'm curious if there is any way to remove just images from the DBXL web service without impacting anything else.  (what we are taking pictures of is all time sensitive, and not terribly useful after 3-6 months, but we need to maintain some of the other data on the form)

*Currently, we are on version 2.6.2011.1211 with a 194 Gb DBXL database containing 11 document types with about 30,000 completed documents total.

Hello jseptor,

 Are the images you are referring to kept as attachments within the XML documents, or are you using some way to save them out to DBXL and SharePoint?  We have techniques for saving attachments out from InfoPath into DBXL or SharePoint and replacing them with links in the XML documents.  This includes the SaveToDbxl and SaveToSharePoint commands in qRules, and the bulk operations described in this document:

http://www.infopathdev.com/files/folders/document_deployer/entry73967.aspx

If you did that, you would have the benefit of having your images in just one place instead of two, and you could go through and periodically delete old images that you don't need.

Does that sound like a viable solution for you?