07-29-2006 01:51 AM
I'm developing an application with LV & DSC 8.0. I'm logging data, A&E in a citadel database.
As REM1 mentioned in message http://forums.ni.com/ni/board/message?board.id=170&message.id=161528&query.id=15913#M161528 , "DSC 7.x and higher make use of Microsoft's free version of SQL Server in conjunction with Citadel for logging alarm/event data. All other data is stored in Citadel itself and never interacts with SQL Server."
I want to know:
If this version of DSC logs Alarm and events to a MSDE database or citadel?
What are the limits of each data storage source?
If A&E is logged into MSDE, is there any lifespan for it?
When we configure a Project library to log data, alarm and event into a database, automatically data is logged to citadel and A&Es are logged into MSDE?
07-30-2006 04:22 PM
The way that I read this page for labview 8 says that the alarms are logged into Citadel.
http://zone.ni.com/reference/en-XX/help/370246D-01/lvdscconcepts/view_alarms_and_events/
08-10-2006 07:59 AM
@Maryam wrote:
I'm developing an application with LV & DSC 8.0. I'm logging data, A&E in a citadel database.
As REM1 mentioned in message http://forums.ni.com/ni/board/message?board.id=170&message.id=161528&query.id=15913#M161528 , "DSC 7.x and higher make use of Microsoft's free version of SQL Server in conjunction with Citadel for logging alarm/event data. All other data is stored in Citadel itself and never interacts with SQL Server."
I want to know:
If this version of DSC logs Alarm and events to a MSDE database or citadel?
What are the limits of each data storage source?
If A&E is logged into MSDE, is there any lifespan for it?
When we configure a Project library to log data, alarm and event into a database, automatically data is logged to citadel and A&Es are logged into MSDE?
DSC 8.x logs alarms/events to CItadel. MSDE is the storage mechanism used by CItadel for the alarm/event data. The reason for doing this is the types of data involved. Single-point (non AE) data is stored in Citadel's compressed data files. Alarm/event data, which is a collection of several different data types all bound together, is stored in MSDE to enable faster, more detailed queries of this more complex data. You can access MSDE directly to view your alarm/event data but there is no need to do so. You can access the alarm/event data using the same methods you would access the single-point data. I mentioned MSDE in the referenced post only to explain, partially, why it was chosen.
Limits of each data storage source -
There is no MSDE imposed lifespan for your AE data that I am aware of and have found no references to such on the web.
You are functionally correct. When you configure a library to log you choose the Citadel database to use. All data associated with that library is sent to Citadel. Citadel stores the single point data in compressed data files and creates an MSDE database to store the AE data. When you use MAX, or the alarm/event VIs, to retrieve this data all requests go to CItadel which gathers the data from it's respective storage location and returns it to the calling program.
12-02-2006 06:04 AM
Hi Robert,
Thanks for your complete answer. I have another problem; in deed I encounter an illogical behavior of "archive trace/s.vi". As I read DSC help on archive methods concept, programmatically database management (exactly archive data, alarm and events) can be done in run time mode. This archival operation includes just copying data not removing them (my application need).
I have a HMI application using
Using a VI running parallel with my GUI, I want to archive data. I guess it should be possible to do this in run time mode, but I encountered an error says "Error -1967386621 occurred at HIST_CompactCORE.vi, Citadel: (Hex 0x8ABC1003) the operation cannot be completed because the resource is in use by another client." I persist again I just copy data.
What's this error for?
12-02-2006 06:04 AM
Hi Robert,
Thanks for your complete answer. I have another problem; in deed I encounter an illogical behavior of "archive trace/s.vi". As I read DSC help on archive methods concept, programmatically database management (exactly archive data, alarm and events) can be done in run time mode. This archival operation includes just copying data not removing them (my application need).
I have a HMI application using
Using a VI running parallel with my GUI, I want to archive data. I guess it should be possible to do this in run time mode, but I encountered an error says "Error -1967386621 occurred at HIST_CompactCORE.vi, Citadel: (Hex 0x8ABC1003) the operation cannot be completed because the resource is in use by another client." I insist again I just copy data.
What's this error for?
12-02-2006 06:11 AM
Hi Robert,
Thanks for your complete answer. I have another problem; in deed I encounter an illogical behavior of "archive trace/s.vi". As I read DSC help on archive methods concept, programmatically database management (exactly archive data, alarm and events) can be done in run time mode. This archival operation includes just copying data not removing them (my application need).
I have a HMI application using
Using a VI running parallel with my GUI, I want to archive data. I guess it should be possible to do this in run time mode, but I encountered an error says "Error -1967386621 occurred at HIST_CompactCORE.vi, Citadel: (Hex 0x8ABC1003) the operation cannot be completed because the resource is in use by another client." I insist again I just copy data.
As mentioned in the following link Overview of Citadel Historical Database Archiving Methods this VI operate on an open database.
What's this error for?
08-26-2007 04:01 AM
08-28-2007 04:41 AM