Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Slow Access 2000 database on Win 2K3 server 1

Status
Not open for further replies.

biketech

MIS
Jul 19, 2004
65
US
Hi everyone.

I just upgraded our network file server to a Small Business Server 2003 box. Now all of a sudden, opening forms and tables on a shared Access 2000 database is really slow. 2-3 minutes to open a form that used to take 30 seconds. I tried compacting and repairing which seemed to take care of it, but then a couple hours later, the same thing.

I tried disabling SMB signing on the 2003 server, but that didn't help.

Any ideas?

Thanks in advance,
Michael
 
Maybe disabling track name autocorrect will speed it up a bit.

ChaZ





There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.
 
Hmm...can you explain a little more what this is?

Thanks.
 
Sorry.

in the d/b, under tools, general tab, there are switches on the right. Perform name auto correct is by default checked. Uncheck it. It may increase performanace. It does for me most of the time.

Chaz

There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.
 
Wow! That made a huge difference. I've never heard of that before. Thanks for the tip! Although the question still remains why this was suddenly a problem on the Win 2K3 server but was never a problem on our old Linux fileserver.

Nonetheless, this saves me a lot of headache.

Thanks again.
 
Glad to help.

I think this function takse advantage of some of the features availale using winserver vs linux. When you switched, it started to try to use them.

ChaZ

There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.
 
Makes sense...I guess I didn't think of that as a server function, but something that would run locally on each client. Thanks...
 
I have recently moved an access 2000 database from a Windows NT4 server to 2003. Since moving the time to open the database by any more than a single user has increased 10 fold.
Any ideas on how to fix this problem??
 
I am not sure, but I am guessing your users have just a link to your MDB file?

Consider trying with one or two clients chaning the link to their copy of access and the MDF file as a cmd line argument, ID

C:\programfiles\blah\Msaccess.exe \\myserver\blah.mdb

I have seen this change make quite a difference sometimes.

Also, check your software firewall settings. I don't know what to check for exactly, but I beleive they can play a part in launching.

ChaZ

There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top