LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Citadel database

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?

0 Kudos
Message 1 of 8
(7,294 Views)

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/

 

  • Historical Data Viewer—You can use the Historical Data Viewer, available in the Measurement & Automation Explorer (MAX), to create views of alarm and event data. You also can use the Historical Data Viewer to archive and export alarm and event data that has been logged to a Citadel database.
  • 0 Kudos
    Message 2 of 8
    (7,274 Views)


    @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 -

    • single-point data - effectively none.  Citadel will continue logging this data until it runs out of free hard drive space.  The compression of the data, however, makes this fairly difficult.
    • alarm/event data -
      • using MSDE - there are 2 limits associated with MSDE. 
        • Your MSDE data cannot be more than 2 Gb per database.  This is only the AE data.  Your single-point data does not factor into this limit.
        • You cannot have more than x MSDE databases per computer.  I think x is 12, but I'm not positive.
      • upgrading to SQL Server 2005 Express - information can be found at microsoft here.  It appears as though this is a free upgrade for MSDE which would, at least, increase the maximum database size if not the database number limit.
      • upgrading to SQL Server - to the best of my knowledge there are no limits using SQL Server but it is not free.

    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.

     

    Regards,
    Robert
    Message 3 of 8
    (7,214 Views)

    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 LV 8.01 and DSC 8.01 with a single process that configured to log data, alarm and events into citadel database. I want to do an archival operation on database every 2 months.

     

    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?

    0 Kudos
    Message 4 of 8
    (6,832 Views)

    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 LV 8.01 and DSC 8.01 with a single process that configured to log data, alarm and events into citadel database. I want to do an archival operation on database every 2 months.

     

    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?

    0 Kudos
    Message 5 of 8
    (6,831 Views)

    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 LV 8.01 and DSC 8.01 with a single process that configured to log data, alarm and events into citadel database. I want to do an archival operation on database every 2 months.

     

    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?

    0 Kudos
    Message 6 of 8
    (6,831 Views)
    HI,Maryam
     
    I encountered  the same problem, did you finish your work successfullly?
     
    Maybe the database must be detached before archived? Or something else?
    0 Kudos
    Message 7 of 8
    (5,085 Views)
    Hi there,
     
    It might be a good idea to post a new question on another forum.  Old forums usually stop being updated in e-mails after a few months.
    If you create a new post and reference this forum you would have a better chance of getting a good answer.
     
    Thanks
     
    AdamB
    Applications Engineering Team Leader | National Instruments | UK & Ireland
    0 Kudos
    Message 8 of 8
    (5,045 Views)