MartyConnelly
martyconnelly at shaw.ca
Mon Mar 3 12:11:00 CST 2003
One other thing that can cause slowness in Win2000 client to Win2000 server. You should try turning off opportunistic locking (OPLOCKS), which allows client side caching of files. Here is two of the links to the info: Configuring Opportunistic Locking in Windows 2000 http://support.microsoft.com/default.aspx?scid=kb;en-us;q296264 Things that slow Jet 4.0 http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B303528#11 MSFT has released a couple of patches for NT/2000 that fix the bugs, but I'd try turning it off before applying them, as it's much simpler. Or apply the latest Win2000 service pack SP-3 This doesn't affect Win9x client to Win2000 server. I believe you can set registry settings on either the client (to enable/disable it from 'asking' for opportunistic locking), or on the server (to enable/disable whether it allows it to be asked). John R. Porter wrote: >Do you have the address of the KB article? > >John R. Porter >I.T.Services >University of Strathclyde >Jordanhill Campus >76 Southbrae Drive >Glasgow >G13 1PP >e-mail: j.r.porter at strath.ac.uk >Tel. 0141 950 3289 > > >-----Original Message----- >From: accessd-admin at databaseadvisors.com >[mailto:accessd-admin at databaseadvisors.com]On Behalf Of Arthur Fuller >Sent: 01 March 2003 13:57 >To: accessd at databaseadvisors.com >Subject: RE: [AccessD] Access & Windows 2000 Performance issues with >linked tables > > >Another approach that does not require moving to SQL and yet delivers all >the speed of a one-MDB solution is to use Replication Manager and place a >local replica on each PC using the app. Then on the server you place the >Replication manager itself and synchronize the local replicas with the >"server" replica every 5 minutes or every hour or whatever interval is >appropriate to your app. > >-----Original Message----- >From: accessd-admin at databaseadvisors.com >[mailto:accessd-admin at databaseadvisors.com] On Behalf Of Mark L. Breen >Sent: March 1, 2003 5:26 AM >To: accessd at databaseadvisors.com >Subject: [AccessD] Access & Windows 2000 Performance issues with linked >tables > >Hello All, > >I was asked recently to move a database that I created three years ago from >a Win NT 4.0 Server server to a new Windows 2000 Server server. > >The database application that I developed is built on a FE, a BE and a MDA >file and also a .mdw file. > >When the backend is on the NT server, performance is fine, but when I move >it to the new Windows 2000 server ( a super duper server with loads of disk >/ ram / processor ), it grinds to a halt. > >To make a long story short, it appears that Microsoft have introduced >something to the Win2K and WinXP OS's that cause linked tables to perform >very slowly. There is an article in the KB about this. > >Their suggestion (as opposed to the fix) is instead of talking to the >properties of the linked tables, to programatically open the backend and >talk directly to the properties of the source tables. > >In my case, I would have to re-write the entire application and it is not >ecomomical to do so, a better alternative to that would be simply to rebuild >the app in SQL and use ADO. > >However, I had another idea which was to bring the BE back into the FE and >leave it as one .mdb file. When I tried that it solved my problem. > >The purpose of this email is to share the information with you guys and ask >if you have experienced this also. > >Incidently, the 'normal' operations such as reading data, querying etc, was >never impaired, it was only when talking to linked tables, > >If you wish to demonstrate this for yourself, create a db with one table and >with about eight fields or so. Save the db as Somename_BE.mdb on a > = Win >2k machine, it can be Pro or Server. Then create another db and link to >Somename_BE.mdb. Finally, let the form wizard create a new form and pull >all the fields in. The form creatation should talk you about ten seconds or >so. If you do the same thing on a Win NT Server, it happens in one second. > >I do not know if this will help anyone, but hopefully it might. > >Best Regards > > >Mark L. Breen >Solution Providers Ltd >Ireland > > >_______________________________________________ >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 > > >