[AccessD] SQL LOG File is Huge! 10GB - Help

Pardon me for jumping in, but a similar issue has been bugging me too. I'm 
not quite sure how this is supposed to work. When you perform a backup in 
SQL Server, all of the committed transactions are supposed to be cleard from 
the transaction log, right? So after performing a backup, I can run a 
function to view the active portion of the log, and there are only a few 
entries in it. But the physical size of the log hasn't gotten any smaller on 
disk. I have the log set to auto-grow. Is it the case that the physical 
allocation of the log grows as the log grows, and then when a backup is 
performed and the comitted transactions are cleared, the physical allocation 
of the log remains at the same siza it grew to, its just empty now. Or if I 
backup a 10 MG log, is the physical size of the log supposed to shrink to 
1MG or whatever. Any clarification regarding this would really help.

Thanks,

Bob


>From: Randall Anthony <ranthony at wrsystems.com>
>Reply-To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>To: "'Access Developers discussion and problem solving'" 
><accessd at databaseadvisors.com>
>Subject: RE: [AccessD] SQL LOG File is Huge!   10GB - Help
>Date: Wed, 8 Oct 2003 09:47:22 -0400
>
>Without looking at the error codes, it sounds like you're not dumping your
>transaction log.  SQL has two settings for backing up files, one were it's
>cumulative (which sounds like what you have set) and one where the file is
>dumped before the backup is created (and you can set the frequency).
>
>-----Original Message-----
>From: Julie Reardon-Taylor [mailto:prosoft6 at hotmail.com]
>Sent: Wednesday, October 08, 2003 9:35 AM
>To: AccessD at databaseadvisors.com; dba-SQLServer at databaseadvisors.com
>Subject: [AccessD] SQL LOG File is Huge! 10GB - Help
>
>
>Hi Group,
>
>All of a sudden, my BEDB.dbf file has grown huge.  The file itself and the
>log file are at 10GB.  I tried shrinking the database, and received a
>message saying that it was successful, however, the files are still the 
>same
>
>size.  I'm receiving an event log error ID 17052 that states that there is
>no more room in the log file.  How can I resolve this problem?  It is
>causing problems on the server because the files are taking up so much
>space.  It is error 9002, severity 17.
>
>
>Julie Reardon-Taylor
>PRO-SOFT OF NY, INC.
>www.pro-soft.net
>
>_________________________________________________________________
>High-speed Internet access as low as $29.95/month (depending on the local
>service providers in your area). Click here.   https://broadband.msn.com
>
>_______________________________________________
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com
>_______________________________________________
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com

_________________________________________________________________
High-speed Internet access as low as $29.95/month (depending on the local 
service providers in your area). Click here.   https://broadband.msn.com