SQL Profiler Temp Space

#1

I'm attempting to run some traces using profiler under SQL2000.

I've noticed that it appears to use some temp space out on the C drive for
some of its operations which is causing some space issues for the underlying
O/S. The trace is running on one server as client against a a database
located on another SQL2000 server.

Is there a way to re point this temp region to a different drive that
contains more space?

#2

I'm pretty certain that Profiler temp space is hardwired to the OS
temp folder (Google and you should find out for sure of you need). You
can change this (OS setting). Or perhaps run server-side traces
instead? They also have a lower overhead compared to client-side
traces...

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

"Tom Frost" <frosty (AT) nospam (DOT) nospam> wrote

Quote:

I'm attempting to run some traces using profiler under SQL2000.

I've noticed that it appears to use some temp space out on the C
drive for
some of its operations which is causing some space issues for the
underlying
O/S. The trace is running on one server as client against a a
database
located on another SQL2000 server.

Is there a way to re point this temp region to a different drive
that
contains more space?

#3

I'm pretty certain that Profiler temp space is hardwired to the OS
temp folder (Google and you should find out for sure of you need). You
can change this (OS setting). Or perhaps run server-side traces
instead? They also have a lower overhead compared to client-side
traces...

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

"Tom Frost" <frosty (AT) nospam (DOT) nospam> wrote

Quote:

I'm attempting to run some traces using profiler under SQL2000.

I've noticed that it appears to use some temp space out on the C
drive for
some of its operations which is causing some space issues for the
underlying
O/S. The trace is running on one server as client against a a
database
located on another SQL2000 server.

Is there a way to re point this temp region to a different drive
that
contains more space?

#4

I'm pretty certain that Profiler temp space is hardwired to the OS
temp folder (Google and you should find out for sure of you need). You
can change this (OS setting). Or perhaps run server-side traces
instead? They also have a lower overhead compared to client-side
traces...

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

"Tom Frost" <frosty (AT) nospam (DOT) nospam> wrote

Quote:

I'm attempting to run some traces using profiler under SQL2000.

I've noticed that it appears to use some temp space out on the C
drive for
some of its operations which is causing some space issues for the
underlying
O/S. The trace is running on one server as client against a a
database
located on another SQL2000 server.

Is there a way to re point this temp region to a different drive
that
contains more space?

#5

I'm pretty certain that Profiler temp space is hardwired to the OS
temp folder (Google and you should find out for sure of you need). You
can change this (OS setting). Or perhaps run server-side traces
instead? They also have a lower overhead compared to client-side
traces...

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

"Tom Frost" <frosty (AT) nospam (DOT) nospam> wrote

Quote:

I'm attempting to run some traces using profiler under SQL2000.

I've noticed that it appears to use some temp space out on the C
drive for
some of its operations which is causing some space issues for the
underlying
O/S. The trace is running on one server as client against a a
database
located on another SQL2000 server.

Is there a way to re point this temp region to a different drive
that
contains more space?

#6

I'm pretty certain that Profiler temp space is hardwired to the OS
temp folder (Google and you should find out for sure of you need). You
can change this (OS setting). Or perhaps run server-side traces
instead? They also have a lower overhead compared to client-side
traces...

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

"Tom Frost" <frosty (AT) nospam (DOT) nospam> wrote

Quote:

I'm attempting to run some traces using profiler under SQL2000.

I've noticed that it appears to use some temp space out on the C
drive for
some of its operations which is causing some space issues for the
underlying
O/S. The trace is running on one server as client against a a
database
located on another SQL2000 server.

Is there a way to re point this temp region to a different drive
that
contains more space?

#7

I'm pretty certain that Profiler temp space is hardwired to the OS
temp folder (Google and you should find out for sure of you need). You
can change this (OS setting). Or perhaps run server-side traces
instead? They also have a lower overhead compared to client-side
traces...

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

"Tom Frost" <frosty (AT) nospam (DOT) nospam> wrote

Quote:

I'm attempting to run some traces using profiler under SQL2000.

I've noticed that it appears to use some temp space out on the C
drive for
some of its operations which is causing some space issues for the
underlying
O/S. The trace is running on one server as client against a a
database
located on another SQL2000 server.

Is there a way to re point this temp region to a different drive
that
contains more space?

#8

I'm pretty certain that Profiler temp space is hardwired to the OS
temp folder (Google and you should find out for sure of you need). You
can change this (OS setting). Or perhaps run server-side traces
instead? They also have a lower overhead compared to client-side
traces...

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

"Tom Frost" <frosty (AT) nospam (DOT) nospam> wrote

Quote:

I'm attempting to run some traces using profiler under SQL2000.

I've noticed that it appears to use some temp space out on the C
drive for
some of its operations which is causing some space issues for the
underlying
O/S. The trace is running on one server as client against a a
database
located on another SQL2000 server.

Is there a way to re point this temp region to a different drive
that
contains more space?

#9

I'm pretty certain that Profiler temp space is hardwired to the OS
temp folder (Google and you should find out for sure of you need). You
can change this (OS setting). Or perhaps run server-side traces
instead? They also have a lower overhead compared to client-side
traces...

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

"Tom Frost" <frosty (AT) nospam (DOT) nospam> wrote

Quote:

I'm attempting to run some traces using profiler under SQL2000.

I've noticed that it appears to use some temp space out on the C
drive for
some of its operations which is causing some space issues for the
underlying
O/S. The trace is running on one server as client against a a
database
located on another SQL2000 server.

Is there a way to re point this temp region to a different drive
that
contains more space?

#10

I'm pretty certain that Profiler temp space is hardwired to the OS
temp folder (Google and you should find out for sure of you need). You
can change this (OS setting). Or perhaps run server-side traces
instead? They also have a lower overhead compared to client-side
traces...

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

"Tom Frost" <frosty (AT) nospam (DOT) nospam> wrote

Quote:

I'm attempting to run some traces using profiler under SQL2000.

I've noticed that it appears to use some temp space out on the C
drive for
some of its operations which is causing some space issues for the
underlying
O/S. The trace is running on one server as client against a a
database
located on another SQL2000 server.

Is there a way to re point this temp region to a different drive
that
contains more space?