Minimize the size of citadel database

[parthabe]

We are logging our digital energy meter data continually, for later use in Reports in the form of MS Excel.

Each meter may consist of N no. of parameters in turn with N no. of shared variables for each of the SV libraries that represent those meter parameters. We are accumulating all the data in csdb files as LV does it automatically for you, when you use the DSC module.

With each day, it grows bigger n bigger in size, for eg, for a week, it is of size >250MB.

When we try to read this csdb file to make Excel reports thro' LV's RGT, it is almost dead-slow in operation. Thats why, we are planning to write to XML files the intermediate data from csbd to XML at the end of each day, and then read this XML file(s) as per the report type, viz, hourly, daily, day-to-day, weekly, monthly or yearly, & accordingly present in Excel.

[Ben]

Hi Partha,

With the app shut-down and logging stopped, this code is what I use in one of my apps that has been collecting DSC data since 2001.

I hope that helps,

Ben

Message Edited by Ben on 06-19-2008 07:56 AM

[parthabe]

Hi Ben,

First, thank you for your help.

But. please tell me where the VI in that BLUE color present in the DSC palette or inside the DSC.llb. I m unable to find it out.

Or, is it possible for you to post that code along with those SubVIs as an llb? Do I bother you too much?

[Ben]

Those blue VI's are just my Event Logging VI. All they do is queue up error cluster to a background logger. i use them in all of my apps so that I can quickly and easily locate any failures. Unlike the NI supplied error handlers they do not stop the application and display an error message. Just use the normal NI stuff for now.

The rest of the code should work without those VI's.

Let me know how the rest of it works out. Long running DSC apps seem to be rare so I want to hear about your experiences.

Ben

[unclebump]

Sounds like a case for using DIADEM maybe. I've got it, but haven't had time to use it yet.