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 |
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
 Posted - 2005-08-25 : 13:29:31
|
We just setup a dev box that is doing nothing but sitting completely idle. The server has 0% CPU used and 200mb of 4gb RAM used. SQL Server is not set to priority.When we try to open profiler on the server locally it opens with no problems but if we attempt to start a trace with the option to save to a table the trace will fail to start. If we start the trace to a file or to the screen it will not stop when the stop button is clicked.Any ideas what would cause this? I tried searching google and found only two instances of this occuring and they were both of no help at all. I know you really should not use profiler on the local machine but that is the business requirements for the next 10 minutes; so it needs to work weather it will be used or not.  DanielSQL Server DBA |
|
|
|
|
|
Profiler: cant save to table or stop trace