Split the Database, Should I do it?

[Joe8915]

I have read a quite a few threads on spiting the database. My database is 50 Meg and running very slow. I have compacted and repair, still the same. This just happen all of sudden. Could that be possible?. What should I look out before I try to spit it?. It’s given that I will make a backup. I am running Access 2003. I have over 150 users.

 

[KenHigg]

:.... I have over 150 users.

150 !! What the most that'll be signed in at any one time? How many workstations do they access it through?

 

[Joe8915]

I could have all 150 at the same time. Would that be a problem?

 

[KenHigg]

I'm guessing you found a new threshold. So you're saying maybe 150 diff workstations as well? If so, my suggestion is to do sqlServer and a web front end. Unless you want to insure all 150 workstations have the fe installed...


Edit: Actually, this amazes me that 150 users are in a non-BE/FE, server .mdb at the same time...

 

[ScottGem]

It amazes me too. Generally, I've heard that Access starts to bog down after 20 concurrent users and that's on a split database.

I will repeat something I have said before. EVERY database that is either multi-user or supported by someone other than the user NEEDS to be split. This is an absolute rule with me. You are asking for trouble if you don't. While you will get better performance if the front end is on the local PC, its not an absolute necessity.

 

[RuralGuy]

To add some detail to the responses of Ken and Scott, here's what MVP Allen Brown has to say on the subject.Split your MDB file into data and application
And here's Tony Toews suggestions on performance: Microsoft Access Performance FAQ