| Author |
transaction log growth
|
|
|
| Hi,
I'm using SqlServer version 2000.80.760.0 and wondering when the last time
the transaction log file grows in size. Is there a way to get that info?
Thanks!
| |
| Hari Prasad 2005-05-26, 1:23 pm |
| Hi,
SQL Server will not store those history in any system tables. The only way
to collect the information is by using SQL profiler. For this
we need to run the profiler all the time.
Thanks
Hari
SQL Server MVP
"Zeng" <Zeng5000@hotmail.com> wrote in message
news:%23tapdThYFHA.796@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I'm using SqlServer version 2000.80.760.0 and wondering when the last time
> the transaction log file grows in size. Is there a way to get that info?
>
> Thanks!
>
>
| |
| David Gugick 2005-05-26, 1:23 pm |
| Zeng wrote:
> Hi,
>
> I'm using SqlServer version 2000.80.760.0 and wondering when the last
> time the transaction log file grows in size. Is there a way to get
> that info?
>
> Thanks!
You can watch for AutoGrow events using Profiler and the SQL Trace API
using server-side traces. In general, you should try and avoid any
auto-grow events because they are cpu and disk intensive operations. Try
and keep your transaction log and data files with sufficient free space.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com
| |
|
| Is there any particular problem with haing the profiler running all the
time? Would the server have to do extra work that it's not normally do
(reporting events etc..)?
Thanks!
"Hari Prasad" < hari_prasad_k@hotmai
l.com> wrote in message
news:%23NIFsxhYFHA.2588@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> SQL Server will not store those history in any system tables. The only way
> to collect the information is by using SQL profiler. For this
> we need to run the profiler all the time.
>
>
> Thanks
> Hari
> SQL Server MVP
>
> "Zeng" <Zeng5000@hotmail.com> wrote in message
> news:%23tapdThYFHA.796@TK2MSFTNGP10.phx.gbl...
time[color=darkred]
info?[color=darkred]
>
>
| |
| David Gugick 2005-05-27, 8:23 pm |
| Zeng wrote:
> Is there any particular problem with haing the profiler running all
> the time? Would the server have to do extra work that it's not
> normally do (reporting events etc..)?
> Thanks!
Profiler is not intended for use in an "Enterprise" manner. Profiler is
a GUI for the SQL Trace API. You should use the api directly by creating
a server-side traces. Profiler can generate much of the T-SQL code for
you from the File - Script Trace menu option. For a small number of
events that do not occur often, you can keep the server-side trace
running all the time. However, you will need to stop it to read the
collected trace data because the data is kept locked in a file while the
trace is running.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com
|
|
|
|