sql server

[alex m]

Problem: Sql server CPU usage is 70%-100% without Lookout running and with Lookout Hypertrend becomes even worse, have to wait for a several seconds to recognize mouseclick. Platform is  Laptop AMD Sempron 3000+,  512MB Windows xp sp2, where memory usage of Sqlserver is allways about 139000KB.

Tried to install Lookout 6.0 Demo version on friends Laptop with Intel Centrino, windows xp sp2, 512 MB. On his computer everything works perfectly right out of the Box, CPU usage is 4%, Sqlserver memory usage about 20000KB. With Lookout hypertend logging nothing changes significaly.

I think the problem is  in the SQL Server program environment and I don't know what causes the problem or how to get it work properly on my machine?

Lookout upgrade to 6.02  and patch did not helped since the problem is resident.

[Ryan.S]

This one may help you.
http://forums.ni.com/ni/board/message?board.id=190&message.id=3160

[alex m]

Thanks for the information.

First I  did archived everything but did not helped that much, as soon the Lookout is up and running, total CPU usage is again 99% based on SQLserver memory usage which jumps to some 139000KB.

But when I start my Lookout process and I execute STOP on SQLserver which immediately shows up a Runtime Error where Visual C++ NIcitadel5 MessageBox pops up and this service is getting  shut down after.

CPU usage gets to normal range below 20%, SQLserver is unloaded from the memory. When I START the SQLserver again, CPU stays in the normal range and SQLserver consumes only 2% of CPU and <7000KB of memory.

I'm still able to rollback the historical data even if this "Nictadl5" service is shut down. 

I dont' know what this service is doing but if it is unloaded from memory SQLserver function gets normal.

If  have lookout running, program/services are : lookout/ lktsrv, lkcitdl, lkads, nimxs, nidmsrv, sqlservr, sqlmangr,

nicitdl5 (if it's not shutdown).

[Ryan.S]

If you stop sqlserver without lookout running, which may not have an error, and then start it, will it work properly?

If you set the "Startup Type" of MSSQLServer to "manual" in "Services", and start it manually after windows starts up, what will happen?

[alex m]

///If you stop sqlserver without lookout running, which may not have an error, and then start it, will it work properly?///

An Error pops up since the NICitadel5 is allready started and running.

///If you set the "Startup Type" of MSSQLServer to "manual" in "Services", and start it manually after windows starts up, what will happen?///

There will be no Error , since the problem with CPU usage is noticable as soon the SQLserver and NICitadel5 are running together.

As a temporary solution it works for me fine without NICitadel5 service.

Maybe something else it's not working properly because of that, but anyway I haven't noticed any other imperfection in my application.

[Ryan.S]

when you start lookout, it will also start citadel service if it's not running. But this seems to be a workaround, if the cpu usage is ok when you stop citadel manually and then run lookout.

[alex m]

I know now the function of NICitadel5 service, it creates the objects inside the database which are checked inside Lookout in >>Edit Database >>  [X]Log to Historical Database, otherwise is not needed.

It is useful to run this service only during the Hypertrend development stage if there is a problem with CPU overload like in my case.

For example, NICitadel5 is also started automaticaly if I add a Trace in NIHypertrend and make a connection to some existing  object in the database. To avoid CPU overload problem I just STOP and START the SQLServer and NICitadel5 is out of game, data is beeing logged uninterrupted and smoothly. It works this way.