Access queries using up space on server's C: drive

  • Thread starter Thread starter Andy S.
  • Start date Start date
A

Andy S.

I have users who are running large SELECT type queries in Access against
a SQL Server via ODBC. What happens is that the c:\documents and
settings\<username>\Local Settings\Temp on the SQL server itself gets filled
until the drive starts running low on space. Other than to free up space on
the server's C: drive, are there any good suggestions to redirecting where
Access stores the temp files?


--

*************************************************
Andy S.
(e-mail address removed)

Please remove "noreply" before replying.

*************************************************
 
yeah

use access data projects instead and keep all your temp tables on the
db server.. where they belong (and have a good io system on the server)
 
Who's profile "<username>" ? And \temp dir gets filled up with what?

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| I have users who are running large SELECT type queries in Access
against
| a SQL Server via ODBC. What happens is that the c:\documents and
| settings\<username>\Local Settings\Temp on the SQL server itself gets
filled
| until the drive starts running low on space. Other than to free up space
on
| the server's C: drive, are there any good suggestions to redirecting where
| Access stores the temp files?
|
|
| --
|
| *************************************************
| Andy S.
| (e-mail address removed)
|
| Please remove "noreply" before replying.
|
| *************************************************
|
|
 
Unfortunately, the end users are creating the queries. I wish I could have
coded everything myself, but that isn't an option. I'm thinking of even
trying to redirect the ODBC log directory setting, but I was hoping there
might be other ideas.

I'd actually rather keep all the temp files locally on the clients where
there is plenty of room.
 
end users CAN create queries in Access Data Projects on the SQL Server
side.. just as easily as on the Access side almost

stored procs are a lot more fun that mdb
 
username would be the end user's profile. I'm not sure of the file
extension, but it is a single large temp file that can grow several hundred
MB in size. I think it is from the ODBC setting for saving long running
queries to a particular folder. I'm not sure why it wouldn't be on the
workstation vs. the server.
 
How did the user profile folders on the SQL server come about? Do they
terminal service into the box? Some details of the files and or file types
may help. I've been running this scenario for a long time and never seen
this before.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| username would be the end user's profile. I'm not sure of the file
| extension, but it is a single large temp file that can grow several
hundred
| MB in size. I think it is from the ODBC setting for saving long running
| queries to a particular folder. I'm not sure why it wouldn't be on the
| workstation vs. the server.
 
why would you ever make a temp file that is hundreds of mb in size?

use some views man
 
Back
Top