2 rating:

1 out of 5

Rate this Document

Why Does sqlservr.exe take up 30-50% of my CPU When I Run My Process or Begin Logging Data?

Primary Software: Lookout
Primary Software Version: 6.0
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem:
I have a Lookout (or DSC) process which, when run causes sqlservr.exe, one of the processes running on my computer, to use 30-50% of my CPU. When I stop the process, CPU usage returns to normal. 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 databasae and the alarm trace can not be deleted by the user.

1. Shutdown Lookout and wait several minutes to ensure any active alarms are stored premanently to the database. Failure to do so will cause any alarms generated after the archive process starts to be lost.
2. Open MAX, 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:

Attachments:





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

Your Feedback!	Poor  |  Excellent							Yes	No
Document Quality?							Answered Your Question?
	1	2	3	4	5
Document needs work? Please tell us why.
Please Contact NI for all product and support inquiries.