Re: Profiler temp file
- From: "Nancy Lytle" <nancy_lytle@xxxxxxxxxxxxxxx>
- Date: Thu, 3 May 2007 16:43:49 -0400
Thanks, with your prodding, I did find what you were talking about and after
some trial and error I got it to work, now I'll do some more testing and
hopefully this will be just what the higher ups needed.
Thanks again,
Nancy
"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message
news:euSdJnajHHA.5044@xxxxxxxxxxxxxxxxxxxxxxx
Yes you are missing the whole point. Profiler is a gui tool that uses the
output of the internal utility called TRACE. You can output directly from
Trace to a file without running profiler at all. Profiler has an enormous
overhead (as you found out) and can significantly impact performance while
running. You do this via a series of tsql commands not with profiler
itself. But you can use Profiler as I mentioned to create the script that
has the series of tsql commands to do the actual work. This first link
shows how to create a script from scratch but if you follow my
instructions fromt he previous post it will make it much easier for you.
All you need to do is to fill in the file name it will create. Have a look
at these:
http://support.microsoft.com/kb/283790 How to create a trace
http://msdn2.microsoft.com/en-us/library/ms191006.aspx
http://msdn2.microsoft.com/en-us/library/aa173875(SQL.80).aspx
--
Andrew J. Kelly SQL MVP
"Nancy Lytle" <nancy_lytle@xxxxxxxxxxxxxxx> wrote in message
news:%23FngeUZjHHA.5012@xxxxxxxxxxxxxxxxxxxxxxx
I'm not sure I am getting what you mean.
We need to run a trace for a period of time to cover while some jobs are
processing etc, and this could take several hours. We do create a trace
and save it to a file or table, but don't you have to leave the Profiler
window open? When I tried to close it, it will stop the trace. And it
is what is displayed in that window that creates the large temp file on
the C drive.
And this could be for either SQL 2005 or 2000, we use one in one
environment (one division) and the other in another environment (the
other division), both are using Windows 2003.
Am I missing something here?
Nancy
"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message
news:OvYsXLZjHHA.492@xxxxxxxxxxxxxxxxxxxxxxx
Well you really shouldn't be using profiler for such things anyway. The
more efficient way to do this is to create a trace and send the trace
events directly to a file on a drive attached to the server. Then you
can copy that file to your local machine and view it in Profiler or dump
it into a table for querying. If you set up a trace definition in
Profiler, run it for a second and then stop it you can go to File -
Script trace to generate an almost ready made script for your trace.
--
Andrew J. Kelly SQL MVP
"Nancy Lytle" <nancy_lytle@xxxxxxxxxxxxxxx> wrote in message
news:O2Gku9YjHHA.1240@xxxxxxxxxxxxxxxxxxxxxxx
Is there any way to move the temp file that is create by Profiler (used
for the datagrid scrolling screen) from the C: drive? Our C drive is
not large enough to allow a long Profiler session, since the Profiler
temp file ends up filling up the C drive.
Nancy
.
- References:
- Profiler temp file
- From: Nancy Lytle
- Re: Profiler temp file
- From: Andrew J. Kelly
- Re: Profiler temp file
- From: Nancy Lytle
- Re: Profiler temp file
- From: Andrew J. Kelly
- Profiler temp file
- Prev by Date: Re: Profiler temp file
- Next by Date: Re: Profiler temp file
- Previous by thread: Re: Profiler temp file
- Next by thread: Re: Profiler temp file
- Index(es):
Relevant Pages
|
