|
While scanning the log files for messages to send, DBREMOTE writes out some 'stuff' to the directory defined by the TMP variable for the user (administrator in our case). Can an engineer explain exactly what it is writing out? We've had some questions about how much space to allocate for such operations when clients want the "C" drive to be small. Are the temp files it writes out proportionate to the size of the log files? (We had some oopsies and ended up with a 50GB log file in less than 24 hours !!! ) |
|
[Preface: As my comments seem to have helped to solve the problem (in contrast to answer the question...), I'm repeating it as an answer - in case Calvin wants to accept it:)] While I can't answer the underlying question (and never have noticed such stuff, only the message files DBREMOTE generates), you should be able to influence the destination of all temporary files SQL Anywhere creates by setting the SATMP (ASTMP for pre-v10) environment variable. SQL Anywhere will then use that variable instead of TMP. Note, SATMP is not created automatically by the installer (in contrast to SQLANY10). You can use the Windows "MyComputer/Properties" dialog to set it (preferable as a system variable). |
While I can't answer your question (and never have noticed such stuff, only the message files DBREMOTE generates), you should be able to influence the destination of all temporary files SQL Anywhere creates by setting the SATMP (ASTMP for pre-v10) environment variable. SQL Anywhere will then use that variable instead of TMP.
Yeah, the only reason we noticed it was because the C: drive filled up completely (it is only a 10GB partition, so it didnt take much).
I'll give that other variable a shot, thanks Volker
Is SATMP a variable I will need to create? I don't see it in the list of current variables.
@Calvin: Yes, SATMP is not created by the installer (in contrast to SQLANY10). You can use the MyComputer/Properties dialog to set it (preferable as a system variable).
Fantastic! Thanks Volker!