[dba-SQLServer] Access disconnecting from sql express DB

J- P jnatola at hotmail.com
Wed Aug 14 13:49:01 CDT 2013


VM Reserved    1469608
VM Committed    1468932
AWE Allocated    0
Reserved Memory    1024
Reserved Memory In Use    0

VM Reserved    1468520
VM Committed    1467904
AWE Allocated    0
MultiPage Allocator    5736
SinglePage Allocator    338912
 

 

 

 

 

 

 

 

 

 

Jean-Paul Natola

 


> From: jnatola at hotmail.com
> To: dba-sqlserver at databaseadvisors.com
> Date: Wed, 14 Aug 2013 14:40:37 -0400
> Subject: Re: [dba-SQLServer] Access disconnecting from sql express DB
> 
> I am making the changed on the 2003 server as per the article, 
> One thing that has me puzzled is that looking at the memory usage of sqlserv.exe its at 1.5gb, i thought sql express was limited to 1 GB of memory , or did I misunderstand what I read?
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Jean-Paul Natola
> 
>  
> 
> 
> > From: fhtapia at gmail.com
> > Date: Wed, 14 Aug 2013 06:39:20 -0700
> > To: dba-sqlserver at databaseadvisors.com
> > Subject: Re: [dba-SQLServer] Access disconnecting from sql express DB
> > 
> > so to help troubleshoot your version of windows 2003 r2 and the sql server
> > engine, follow the tips in this kb
> > 
> > http://support.microsoft.com/kb/942861
> > 
> > and report back if any of it helps (or is unhelpful).
> > 
> > good luck!
> > 
> > -Francisco <http://twitter.com/seecoolguy>
> > 
> > 
> > 
> > 
> > On Wed, Aug 14, 2013 at 6:36 AM, Francisco Tapia <fhtapia at gmail.com> wrote:
> > 
> > > 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
> > >>
> > >>
> > >
> > _______________________________________________
> > dba-SQLServer mailing list
> > dba-SQLServer at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> > http://www.databaseadvisors.com
> > 
>  		 	   		  
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
> 
 		 	   		  


More information about the dba-SQLServer mailing list