Normaliztion of tables

I am using Access 2000 on a computer running Win 2000. I have created a
database with all the tables in a seperate database. All the
forms/macros/queries reside together in another database. The databases are
accessed by my biomed group via a WAN. As I upgrade features in the forms I
roll them out to our server for the group to utilize with minimal downtime.

MY question: I normalized the tables as much as possible because that was
what I was taught. I am seeing the databse starting to grow sluggish as it
continues to grow. Ignoring other contributing factors - can too much
normalization contribute to a sluggish database? I am thinkin of redoing the
database only this time with less normalization.

In my opinion, normalization should be the last to go.
Things you should try before then...
Performance analyser can recommend new indexes
Compaction of both databases
Defragging the backend hard disk
Network performance analysys
Upsizing the backend to sql server

"Biomed" wrote:

I am using Access 2000 on a computer running Win 2000. I have created a
database with all the tables in a seperate database. All the
forms/macros/queries reside together in another database. The databases are
accessed by my biomed group via a WAN. As I upgrade features in the forms I
roll them out to our server for the group to utilize with minimal downtime.

MY question: I normalized the tables as much as possible because that was
what I was taught. I am seeing the databse starting to grow sluggish as it
continues to grow. Ignoring other contributing factors - can too much
normalization contribute to a sluggish database? I am thinkin of redoing the
database only this time with less normalization.

Using Access across a WAN is not advisable. Besides the potential for
database corruption, it will be much slower than a direct LAN link.


On Tue, 19 Apr 2005 13:31:02 -0700, Biomed
wrote:

I am using Access 2000 on a computer running Win 2000. I have created a
database with all the tables in a seperate database. All the
forms/macros/queries reside together in another database. The databases are
accessed by my biomed group via a WAN. As I upgrade features in the forms I
roll them out to our server for the group to utilize with minimal downtime.

MY question: I normalized the tables as much as possible because that was
what I was taught. I am seeing the databse starting to grow sluggish as it
continues to grow. Ignoring other contributing factors - can too much
normalization contribute to a sluggish database? I am thinkin of redoing the
database only this time with less normalization.



**********************

remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

=?Utf-8?B?QmlvbWVk?= wrote in
:

The databases are
accessed by my biomed group via a WAN.

I'm with Jack on this: Jet is a file-sharing architecture, not a client
server one and will be both dangerous and slow over a WAN. I note that you
talk about databases (plural) being served over the WAN -- the front ends
really should be stored on local HDDs and that will save a bit, but having
the back end across a WAN is pretty much a non starter.

Suggestion: change the back end to MSDE or another version of SQL Server.
Run the front end via ODBC or, perhaps, reprogram into an ADP.

Hope that helps


Tim F