Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI
4 ratings:
 2.25 out of 5     Rate this Document

Why Does sqlservr.exe take up 30-50% of my CPU?

Hardware: PXI/CompactPCI>>Controllers

Problem:
In task manager, I see the sqlservr.exe process using 30 to 50% of my CPU. What is causing this behavior and how do I work around it?

Solution:
This problem occurs when there is an empty alarm trace in the Citadel database. This CPU usage can be observed when a Lookout or DSC process starts utilizing that specific database.

  1. If you are using Lookout, shutdown Lookout. If you are using DSC, stop the shared variable engine from the Variable Manager. Wait several minutes to ensure any active alarms are stored permanently to the database. Failure to do so will cause any alarms generated after the archive process starts to be lost.
  2. Open Measurement & Automation Explorer, then browse to the database that is causing the issue.
  3. Right-click on the database and choose "Archive"
  4. When prompted to select a destination database, create a new database in known location.
  5. Let the archive process complete.
  6. You now have the option of reconfiguring the process to log to the new database, or you can detach the original database, move it to a backup location, then reattach the newly created archive with the same name as the original database.



Related Links:
KnowledgeBase 2X884Q2P: How Do I Configure Alarm Areas in the LabVIEW DSC Module?
KnowledgeBase 33GA0FQA: How Can I Delete Old Alarms from the Citadel Alarm Database?

Attachments:





Report Date: 11/11/2005
Last Updated: 03/12/2009
Document ID: 3RABGR6K

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
  1 2 3 4 5
Please Contact NI for all product and support inquiries.submit