I apologize for not providing enough information initially. It's a SQL
7.0 SP4 installation that accepts almost no user connections at all. It
only runs batch processes for keeping data in sync between an AS/400 and
another SQL 7.0 SP4 server.
When I've run the sp_who and sp_who2 on the system through query analyzer in
the past, I haven't seen anything that would lead me to think it was eating
up all of the CPU. In fact it looks remarkably low on load.
I get kind of lost when running profiler because I'm somewhat new to SQL
server and don't really know what to look for when I'm creating the trace.
Thanks so much for your assistance.
Joe
Profiler will allow you to see the sql statements as they are submitted to
the database.
You can also
exec sp_who
or
exec sp_who2
within Query Analyzer to see how many connections there are
--
Keith, SQL Server MVP
Quote:
> What's the best way to determine what is causing SQL 7 SPU spin?
> Joe Cormane