I was working with the softgrid data store and found out that all the information regarding the application usage and all goes in to the data store, this might burden the data store quite a bit so I was thinking of redirecting the data generated for various reports to some other secondary database (may be on a different machine) instead of the primary database so as to save it from unnecessary transactions.
Now my question is, how feasible it is? How can it be done?
I have identified some stored procedures and tables related to the report generation, how feasible is it to modify those stored procedures.
Waiting for any kind of help,
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


The Softgrid database is incredibly straightforward but you will have to do some customization to move that data off to a different SQL datastore if you think the reporting burden is going to be that bad. I haven't seen the SQL server get terribly overloaded but then again most of my clients are not using the licening / useage feature all that much. If you need to get the data over to another then SQL replication should do it. SQL replication is already used on sites that need the same Softgrid database replicated over to different servers that are geographically seperated. The tables involved should be independant of the rest of the databases but I would have to poke into the database to give you recommendeations. I think the database is straightforward but let me know if you are having issues.
Answered 01/24/2007 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment