Hallo Markus,
die Berichte im SSMS greifen auf die vorhandenen Trace-Files zu.
Siehe hierzu auch:
http://www.insidesql.org/blogs/cmu/sql_server/woher-kommt-sql-trace-1
Du könntest aus den aktuellen Trace-Files für die aktuelle Datenbank das Wachstum wie folgt ermitteln:
declare @curr_tracefilename varchar(500)
declare @base_tracefilename varchar(500)
declare @indx int
select @curr_tracefilename = path from sys.traces where is_default = 1
set @curr_tracefilename = reverse(@curr_tracefilename)
select @indx = PATINDEX('%\%', @curr_tracefilename)
set @curr_tracefilename = reverse(@curr_tracefilename)
set @base_tracefilename = LEFT(
@curr_tracefilename,len(@curr_tracefilename) - @indx) + '\log.trc';
select (dense_rank() over (order by StartTime desc))%2 as l1
, convert(int, EventClass) as EventClass
, DatabaseName
, Filename
, (Duration/1000) as Duration
, StartTime
, EndTime
, (IntegerData*8.0/1024) as ChangeInSize
from ::fn_trace_gettable( @base_tracefilename, default )
where EventClass >= 92 and EventClass <= 95 and ServerName =
@@servername and DatabaseName = db_name()
order by StartTime desc ;
Einen schönen Tag noch,
Christoph
--
Microsoft SQL Server MVP
www.insidesql.org/blogs/cmu
