hi,

i am running sql server 2005 profiler on a system, where not much space is
left on c:\. that way i have configured profiler to write all files on d:\,
which is more suitable here. however i clearly can see that c: is somehow
affected as space is getting less and less here. as soon as the profiler is
stopped and restarted - space is facing the same size as in the beginning on
c:\.

i am wondering, why it is like this in order to "disable" it. errorlog is
facing the same size; the same for eventlogs...

--
thanks in advance / danke im voraus, fritz
--
Fritz Theiss

Are you sure that the problem is SQL Profiler? How do you create the trace
files (with sp_trace_create or maybe Profiler is running?)


--
--
Un saludo
-------------------------------
www.navento.com
Servicios de Localización GPS


"Fritz Theiss" wrote:

thx so far.

to answer the questions:

1) well, i do run sql profiler, nothing with sp_trace_create.
2) yes, i am sure - as soon as profiler is stopped, space on c:\ gets freed.

--
thanks in advance / danke im voraus, fritz
--
Fritz Theiss



"Carlos Sacristan" wrote:

Have you modified the %TEMP% and %TMP% environment variable to point to D:?
If not, might be worth a try.
Right Click in My Computer -> Properties -> Advanced -> Environment
Variables

--
Regards,
LeoPasta - http://sqlblogcasts.com/blogs/leopasta/default.aspx

"Fritz Theiss" <FritzTheiss (AT) discussions (DOT) microsoft.com> wrote

no, i did not as it was not necessary: two files are in %tmp% and %temp%
(both sharing the same physical location), but they are of size 0 bytes.

this does not seem to be the problem...

--
thanks in advance / danke im voraus, fritz
--
Fritz Theiss



"LeoPasta" wrote:

Profiler uses some temp directory. AFAIK, this is the same as where
you point Windows TMP or TEMP to. I strongly encourage you to do
server side tracing instead of profiler.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Fritz Theiss" <FritzTheiss (AT) discussions (DOT) microsoft.com> wrote in
message newsC2C67A0-9CFF-4404-8D24-49F019C8D40D (AT) microsoft (DOT) com...

Fritz Theiss (FritzTheiss (AT) discussions (DOT) microsoft.com) writes:
That may be because they are open for writing, so the real size does not
display.

If you are short on space on C, you should change TEMP and TMP anyway.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

OMHO, you *should* use a server side trace and manage with the sp_trace_*
stored procedures if you have a lot of data being traced. You can use the
Profiler GUI to script the trace and/or to display the trace data afterward.
See
http://weblogs.sqlteam.com/dang/arch...-Profiler.aspx
for more information.

--
Hope this helps.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"Fritz Theiss" <FritzTheiss (AT) discussions (DOT) microsoft.com> wrote

i figured the problem out:

the environment variables of the user pointed to c:\. here i could find
..tmp-files with a size of more than 4 gb. as soon as profiler was ended these
files passed by.

i now configured these user environment variables to another partition...

--
thanks in advance / danke im voraus, fritz
--
Fritz Theiss



"Erland Sommarskog" wrote: