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 |
|
Lumbago
Norsk Yak Master
3271 Posts |
 Posted - 2004-03-30 : 08:55:05
|
| I just started a trace here that logs to a table on my production database. However I only trace deadlocks so it will (hopefully) be a while before I get any results. Is it possible to close the profiler and leave the trace running, and in that case how will I then be able to stop the trace when I'm finished? Maybe it's even a good thing to leave it running for all I know...EDIT: I started the trace from my local laptop but the trace is running on the prod database and logs to the same prod-server but on a different database.--Lumbago"Real programmers don't document, if it was hard to write it should be hard to understand" |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-03-30 : 09:44:30
|
| You can save the trace as a script. You can then start or start it as you wish without using Profiler. YOu can also schedule it from a job.The only problem is that it won't write to a table. It would write to a file. You would have to then import to a table. Graz has a tool that automates all this for you.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
|
|
|
Profiler