Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
james75
Starting Member
2 Posts |
Posted - 2008-03-12 : 20:06:21
|
| This has been driving me crazy.First noticed it when I went from JIT compiling of my .net app to pre-compiled via the command prompt, although I can't see that that's go anything to do with it...My database is around 2gb and I'm using service broker.If I drop a new version of my app into production, sqlserver.exe goes nuts and eats up the cpu.Tonight, I stopped IIS and SQL Server, then dropped a new version in. I hadn't re-started IIS at this point... As soon as I started SQL Server, off it went again - eating up the CPU. I quickly launched a trace via the Profiler - no activity showing.So, I started IIS after a couple of mins (still with the high cpu) and then just waited. After about 10 mins, SQL Server settled down and everything was normal again.What is it doing when I start the SQL Server service?Si |
|
|
james75
Starting Member
2 Posts |
Posted - 2008-03-12 : 20:08:46
|
| Couple of things I forgot to mention...I'm using Win2003 64-bit, 64-bit sql server standard ed.If I run up FileMon (sysInternals), I see masses of READS against my database file. Remember, this is even when no clients are connected and IIS is stopped... |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-03-12 : 22:52:18
|
| Use sp_who2 to check how many connections in sql. |
 |
|
|
|
|
|