[dba-SQLServer][AccessD] Re: SQL LOG File is Huge! 10GB - Help

I believe Full Recovery Model gives the best chance to recover from a 
failure in a transactional environment.  I copied the following from SQL 
Server Books Online:

"Full Recovery provides the ability to recover the database to the point of 
failure or to a specific point in time. To guarantee this degree of 
recoverability, all operations, including bulk operations such as SELECT 
INTO, CREATE INDEX, and bulk loading data, are fully logged. "

My organization doesn't really need Full Recovery because our data doesn't 
change very often, and we aren't doing a lot of transactions.  With tape 
backups, we can recover from the previous day, which is ok for us.

Paul Liadis
Penn State University


At 09:23 AM 10/8/2003 -0700, you wrote:
>What are the benefits of choosing Full Recovery Model?
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Paul Liadis
>Sent: Wednesday, October 08, 2003 8:17 AM
>To: Access Developers discussion and problem solving
>Subject: [dba-SQLServer][AccessD] Re: SQL LOG File is Huge! 10GB - Help
>
>
>We ran into this once, and here is what was causing our problems.  If you
>look at the properties of your database in Enterpirse Manager,  there is a
>tab that says Options.  On this tab, there is a dropdown for recovery
>model.  Our logs were growing huge because we chose Full in the Recovery
>Model dropdown.  To fix the problem we chose Simple and this significantly
>reduced the size of our Transaction Logs.
>
>Paul Liadis
>University Budget Office
>Penn State University
>
>At 09:35 AM 10/8/2003 -0400, you wrote:
>
> >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
> >
> >_______________________________________________
> >dba-SQLServer mailing list
> >dba-SQLServer at databaseadvisors.com
> >http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> >http://www.databaseadvisors.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
>
>
>_______________________________________________
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com