https://www.infopathdev.com:443/forums/61.aspxQdabra Database Accelerator (DBXL) simplifies connecting InfoPath to SQL Server and SharePoint for codeless storage, permissions, workflow, and reporting on InfoPath forms. This forum also supports users of Qdabra's WSSP.enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/81708.aspxThu, 16 Aug 2012 18:13:56 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:81708DC Forms0https://www.infopathdev.com:443/forums/thread/81708.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&PostID=81708<p>We experienced the consumption of all system memory issue. This would be useful information in the installation guide for DBXL.</p>https://www.infopathdev.com:443/forums/thread/81657.aspxWed, 15 Aug 2012 15:15:01 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:81657Jim Cantwell0https://www.infopathdev.com:443/forums/thread/81657.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&PostID=81657<p>Your DBA will want as much information as possible about your applications data storage requirements.&nbsp; What are typical sizes for XML being saved, how many documents you expect to be saving monthly and how frequent updates are being made.&nbsp; This information will help ensure the drives for the databases are sufficiently sized.&nbsp; And if you have lots of users with frequent updates, transaction logs at short intervals will be warranted.&nbsp; DBXL also has a document history option, so each update could add to the storage requirement.&nbsp; If you will be using document history, make sure your DBA is aware of document sizes and expected number of updates per document.</p><p>Let your DBA know that DBXL v2.6 utilizes the SQL Server CLR.&nbsp; It is best to set a max memory limit on the SQL Server instance to prevent consuming all system memory.&nbsp; While SQL Server should relinquish memory back to the OS if requested, there are situations where SQL Server does not heed these requests.</p><p>DBXL also utilizes XML indexes to enable reporting and fast querying based on form&#39;s xml content without first requiring shredding to database tables.&nbsp; This functionality comes with a storage cost, which can be 50% or more of the content being stored.&nbsp; Starting with basic calculations of storage needs, your DBA can just increase the estimated storage needs.</p>https://www.infopathdev.com:443/forums/thread/81608.aspxMon, 13 Aug 2012 14:16:48 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:81608DC Forms0https://www.infopathdev.com:443/forums/thread/81608.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&PostID=81608<font size="3" face="Times New Roman"> </font><p style="margin:0in 0in 0pt;" class="MsoNormal"><font size="3"><font face="Calibri">I have a dedicated instance of MS SQL Server 2008 R2 supporting DBXL. Currently the server instance is set with a default configuration. Are there any recommendations on configuring and optimizing the database server that I can pass on to our DBA?</font></font></p><font size="3" face="Times New Roman"> </font>