Francisco Tapia
fhtapia at gmail.com
Wed Aug 14 08:36:39 CDT 2013
Hey JP, I would grow the log to at least 10%, this will keep it from fragmenting too quickly, in general this is the size you want for your transaction log. (the exception is if you perform large table modifications that eat up larger than the 10% size you set up) lastly, if you can I would build a small c# windows app, that hooks into your database. and have it email you or alert you whenever it disconnects from the server. The problem you are experiencing may still be database engine related. -Francisco <http://twitter.com/seecoolguy> On Tue, Aug 13, 2013 at 7:54 PM, J- P <jnatola at hotmail.com> wrote: > So I changed recovery to simple, did a shrink via smss and selected log, > shrink, reclaim unused space > and WOW did it shrink, it went down to 1MB , thats not even 1 % , much > less 10% of the DB size (hope I didnt muck it up) > > Then > I reverted back to full recovery , ran a full backup and a log backup > and its still working, as far as versions they are the following ; > > 2003 r2 sp2 > sql 9.0.5000 sp4 > > What > are items I should look for in a trace that should be considered > "flags" - this DB started in access 97, went through many hands and > "coders" (using the term loosely,) then went to sql express , and the > front end has gone from Access 97 to 2000, , xp, 2003, and now on 2010 > > So there are many places that it could go wrong- If I were to open a PSS > case, should I open an Access 2010 case or SQL case? > > > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > >