peter-661823 (12/13/2012)

---

Thanks for Reply
I looked at the growing Events as told in the link, with the script
ECLARE @path NVARCHAR(260);

SELECT @path = REVERSE(SUBSTRING(REVERSE([path]), CHARINDEX('\', REVERSE([path])), 260)) + N'log.trc'
FROM sys.traces WHERE is_default = 1
SELECT DatabaseName,
[FileName],
SPID,
Duration,
StartTime,
EndTime,
FileType = CASE EventClass
WHEN 92 THEN 'Data'
WHEN 93 THEN 'Log'
END
FROM sys.fn_trace_gettable(@path, DEFAULT)
WHERE EventClass IN (92,93)
ORDER BY StartTime DESC;

Results in:
tempdb tempdev 186 0 2012-12-13 09:17:33.667 2012-12-13 09:17:33.667 Data
tempdb tempdev 63 0 2012-12-13 09:12:28.380 2012-12-13 09:12:28.380 Data
tempdb tempdev 64 13000 2012-12-13 09:07:49.397 2012-12-13 09:07:49.410 Data
tempdb tempdev 63 0 2012-12-13 09:03:23.287 2012-12-13 09:03:23.287 Data
tempdb tempdev 230 0 2012-12-13 09:00:00.127 2012-12-13 09:00:00.127 Data
tempdb tempdev 64 0 2012-12-13 08:56:20.127 2012-12-13 08:56:20.127 Data
tempdb tempdev 64 0 2012-12-13 08:52:58.670 2012-12-13 08:52:58.670 Data
tempdb tempdev 186 0 2012-12-13 08:49:55.840 2012-12-13 08:49:55.840 Data
tempdb tempdev 71 0 2012-12-13 08:45:03.247 2012-12-13 08:45:03.247 Data
tempdb tempdev 204 0 2012-12-13 07:58:01.040 2012-12-13 07:58:01.040 Data
tempdb tempdev 63 0 2012-12-13 07:53:40.587 2012-12-13 07:53:40.587 Data
tempdb tempdev 63 16000 2012-12-13 07:50:01.443 2012-12-13 07:50:01.460 Data
tempdb tempdev 109 13000 2012-12-13 07:46:32.757 2012-12-13 07:46:32.770 Data
tempdb tempdev 117 13000 2012-12-13 07:43:35.787 2012-12-13 07:43:35.800 Data
TempDB is growing very frequent (and only for a small amount) at the moment because we restart SQL Service last night, and autogrowing of TempDB is set to 10%. The growing event itself has no impact for all the users currently working on our databases.

Does the SPID mean that this SPID is responsible for this growing event?
So it seems that the growing event ist independent from the maintaince.
Peter

peter-661823 (12/14/2012)

---

I have also seen that TempDB growing only occurs at busineshours, in the night wíth less people working, no growing of TempDB took place.

peter-661823 (12/14/2012)

---

Thanks again for answer
I understand your way to set autogrow "grow by Megabytes", I think I will do this in future too. But this does not solve the reason why the tempDB starts to grow last summer. Is it possible that raising user count and a raising count of Data overall brings this 8GB server to a memory bottleleck?
To less physical memory seems to cause more use of TempDB. But on the other hand the TempDB Space is almost unused (free).
I have also seen that TempDB growing only occurs at busineshours, in the night wíth less people working, no growing of TempDB took place.
So I used DBCC MEMORYSTATUS for the first time. See below. At the moment I try to interpret the output by using http://support.microsoft.com/kb/907877.

Thanks for Help.
Peter

Noetic DBA (12/14/2012)

---

Also, the tempdb is growing because it is not checkpointing properly.