Seem to recall that one of these is used when executing stored procedures -
think it's tempdb. Seems as if this database grows and doens't shrink
automatically - what do i do ... select autoshrink or put a task into my dts
package that truncates the database when my transfer is completed.

Or shouldn't I mess with these..?

Example of tempdb now: 655 size, 1,00 used of database, 0,74 size, 0,49 used
of log

--Michael V.

In message <#Pxd9WAYEHA.4092 (AT) TK2MSFTNGP11 (DOT) phx.gbl>, Michael Vardinghus
<michaelvardinghus (AT) notexisting (DOT) com> writes
There is very little that should ever induce master to grow. You
shouldn't be adding objects or storing data inside master.

Depending on what you are doing tempdb can grow quite large, and this is
acceptable. It can be used explicitly as a working area, and will also
be used internally by SQL Server during certain operations. I would not
recommend shrinking tempdb, otherwise next time it requires more space
it will auto-grow again, which is quite an expensive operation, which
will slow down the transaction that requires more space. I'd recommend
that you actually use ALTER DATABASE dbname (file='tempdev',size=xxxx).
This will save auto-growth operations for the reasons above, which at
the very least may happen after every server restart since tempdb is
re-created on restart.

The log file can also grow quite large, but since it uses the Simple
recovery model, it will clear down automatically on checkpoints


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org