database logging takes a looong time

[david_jenkinson]

Hello,

We run tests overnight, sometimes longer than 24 hours.  I have noticed, when logging to the database, it takes a very long time to complete.  For example, this morning when finishing an overnight test run, it took about 10 seconds for the logging the report, but about 5 minutes for logging to database. 

Does anyone have any suggestions on how to cut this time down?  When running for 24+ hours, it's a situation where you just walk away and come back an hour later to check the logging process.

Thanks

[Scott_Richardson]

David -
Report generation is faster than database logging because serializing a text stream to file is much faster than logging individual values to specific columns in a set of tables.

To help, it might be helpful for us to know the following:

1. What version of TestStand are you using?
2. What report type, HTML, TXT, etc. are you using?
3. How many step results are in the report and/or are you logging to database for that 24 hour run? The same?
4. Are you logging the same information to the database that appears in the report for each step result?
5. What database are you logging to and what schema are you using? If you have modified the schema, what is it most like in the default set or is it very different?
6. Is there a subset of the database data that you could log instead of logging all results? If yes, what type of data would you want to possibly exclude to improve performance?