Database log files

Does anyone know of anyway to read the transaction logs? The reason why I am
curios is, the transaction logs are way to large for the amount of
transactions we are running(yes, the transaction logs are set to
automatically grow). Our application would not send that amount of
transactions to the database. The other thing I am thinking is that there is
another db within this sqlserver that I think access this DB and I think the
transaction logs would prove this.
Thanks for your assistance in advance....
I've listed three log reader tools on my links page:
http://www.karaszi.com/SQLServer/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"TJ" <TJ@.discussions.microsoft.com> wrote in message
news:92CF3A8E-4DA0-4E1B-BCA8-EC4491DCAFED@.microsoft.com...
> Does anyone know of anyway to read the transaction logs? The reason why I am
> curios is, the transaction logs are way to large for the amount of
> transactions we are running(yes, the transaction logs are set to
> automatically grow). Our application would not send that amount of
> transactions to the database. The other thing I am thinking is that there is
> another db within this sqlserver that I think access this DB and I think the
> transaction logs would prove this.
> Thanks for your assistance in advance....
|||What recovery mode are you in? If it is FULL and you don't issue regular
Log backups it will continue to grow and grow. Change it to simple mode and
you should not see it grow any more. If you really want to see what is
happening on the server you should use Profiler or Trace.
Andrew J. Kelly SQL MVP
"TJ" <TJ@.discussions.microsoft.com> wrote in message
news:92CF3A8E-4DA0-4E1B-BCA8-EC4491DCAFED@.microsoft.com...
> Does anyone know of anyway to read the transaction logs? The reason why I
> am
> curios is, the transaction logs are way to large for the amount of
> transactions we are running(yes, the transaction logs are set to
> automatically grow). Our application would not send that amount of
> transactions to the database. The other thing I am thinking is that there
> is
> another db within this sqlserver that I think access this DB and I think
> the
> transaction logs would prove this.
> Thanks for your assistance in advance....
|||TJ
Another option to consider is the Bulk-Logged recovery mode. Bulk-logged
has better performance than Full with large bulk inserts and bcp operations
because the transaction log files should not grow as quickly as a result of
only recording complete transactions. In other words, you sacrifice the
ability to recover row by row that might occur with large batches.
Regards,
Keith
This posting is provided "as is" without inferring rights or warranties.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eOihJpswFHA.2076@.TK2MSFTNGP14.phx.gbl...
> What recovery mode are you in? If it is FULL and you don't issue regular
> Log backups it will continue to grow and grow. Change it to simple mode
> and you should not see it grow any more. If you really want to see what
> is happening on the server you should use Profiler or Trace.
> --
> Andrew J. Kelly SQL MVP
>
> "TJ" <TJ@.discussions.microsoft.com> wrote in message
> news:92CF3A8E-4DA0-4E1B-BCA8-EC4491DCAFED@.microsoft.com...
>