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:

tempdbtempdev18602012-12-13 09:17:33.6672012-12-13 09:17:33.667Data

tempdbtempdev6302012-12-13 09:12:28.3802012-12-13 09:12:28.380Data

tempdbtempdev64130002012-12-13 09:07:49.3972012-12-13 09:07:49.410Data

tempdbtempdev6302012-12-13 09:03:23.2872012-12-13 09:03:23.287Data

tempdbtempdev23002012-12-13 09:00:00.1272012-12-13 09:00:00.127Data

tempdbtempdev6402012-12-13 08:56:20.1272012-12-13 08:56:20.127Data

tempdbtempdev6402012-12-13 08:52:58.6702012-12-13 08:52:58.670Data

tempdbtempdev18602012-12-13 08:49:55.8402012-12-13 08:49:55.840Data

tempdbtempdev7102012-12-13 08:45:03.2472012-12-13 08:45:03.247Data

tempdbtempdev20402012-12-13 07:58:01.0402012-12-13 07:58:01.040Data

tempdbtempdev6302012-12-13 07:53:40.5872012-12-13 07:53:40.587Data

tempdbtempdev63160002012-12-13 07:50:01.4432012-12-13 07:50:01.460Data

tempdbtempdev109130002012-12-13 07:46:32.7572012-12-13 07:46:32.770Data

tempdbtempdev117130002012-12-13 07:43:35.7872012-12-13 07:43:35.800Data

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