Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > Microsoft Office > Access and Access VBA > Access
Password Reminder
Register
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old February 12th, 2004, 05:59 PM
Authorized User
 
Join Date: Nov 2003
Location: , , .
Posts: 14
Thanks: 0
Thanked 0 Times in 0 Posts
Default Table Performance

Hello,

I am creating an order entry system for a print shop that has many options for custom printing. I know about keeping tables small for performance issues...but my order entry table has grown to 100 fields. The table takes about 30 seconds to open to view records or modify the table.
Besides breaking he table up into smaller units any suggestions to increase performance?


Reply With Quote
  #2 (permalink)  
Old February 12th, 2004, 06:23 PM
Authorized User
 
Join Date: Dec 2003
Location: Middletown, CT, USA.
Posts: 81
Thanks: 0
Thanked 0 Times in 0 Posts
Default

How many records do you have in the table?? Perhaps you can archive some of them.

Beyond that, what types of fields do you have. 100 seems like a table that can probably be normalized into several smaller tables.

John

Reply With Quote
  #3 (permalink)  
Old February 12th, 2004, 11:45 PM
sal sal is offline
Friend of Wrox
 
Join Date: Oct 2003
Location: Clarksville, TN, USA.
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts
Default

100 fields is too many fields. Are you keeping a lot of bit (check boxes) data types in the table?

Make sure to use indexes on your table. Are you using this over a network?



Sal
Reply With Quote
  #4 (permalink)  
Old February 16th, 2004, 06:33 PM
Authorized User
 
Join Date: Jun 2003
Location: Glendale, AZ, USA.
Posts: 75
Thanks: 0
Thanked 0 Times in 0 Posts
Default

you should check to make sure you have the latest SP for Jet installed. SP8 is the current rev number. There were some perfomance issues with earlier SP revs.

http://www.microsoft.com/downloads/d...DisplayLang=en

HTH,
Mike
Reply With Quote
  #5 (permalink)  
Old February 16th, 2004, 10:21 PM
Friend of Wrox
 
Join Date: Jul 2003
Location: Houston, Texas, USA.
Posts: 174
Thanks: 0
Thanked 0 Times in 0 Posts
Default

DON'T DO IT!! SP-8 is a nightmare!! See the thread about 'Sandbox Mode' and then think again!

Regards,

Beth M
Reply With Quote
  #6 (permalink)  
Old February 16th, 2004, 11:22 PM
sal sal is offline
Friend of Wrox
 
Join Date: Oct 2003
Location: Clarksville, TN, USA.
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks Beth. It is not always best to get the latest SP from MS for Access. Always check for bugs on SPs in forums. I have found that to be helpful.



Sal
Reply With Quote
  #7 (permalink)  
Old February 16th, 2004, 11:32 PM
Authorized User
 
Join Date: Jun 2003
Location: Glendale, AZ, USA.
Posts: 75
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Check out the MS website before installing SP8. I installed it back in October and haven't ran into any issues. I think the issues depend on the specific delivery of your application to end users an probably a whole host of other issues.

Your question was how to increase performance without re-designing your database, SP8 will give you that especially if you are using an earlier version with known documented problems with performance.

Bottom line, explore all and read all before installing.

Thanks,
Mike
Reply With Quote
  #8 (permalink)  
Old February 17th, 2004, 12:17 AM
Friend of Wrox
 
Join Date: Jul 2003
Location: Houston, Texas, USA.
Posts: 174
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Mike (Dataman), I hate to tell you this, but applying a newer SP for jet isn't going to make a table perform any better if it is poorly designed. Here in the South, we have a saying for this, "Facts Are". SP's weren't created as a 'fix-all' for poorly designed databases. It was created so hackers couldn't run malicious macros against VBA code in an Access database. Another one of Bill's 'fixes' that affect how we do our jobs.

Additionally, with 100 fields in a single table, I would say it is time to step back and look at normalization of the data.

Regards,

Beth M
Reply With Quote
  #9 (permalink)  
Old February 17th, 2004, 10:10 AM
Authorized User
 
Join Date: Jun 2003
Location: Glendale, AZ, USA.
Posts: 75
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Beth,
  I don't disagree with you. A poorly designed database is a poorly designed database. However, 100 fields is not a huge amount especially of fields. I suspect that the table is not the problem, more likely it is the network, or file server, or the logic of the form that is the culprit.

  There are known performance issues with SP6 and prior. Since SP8 is the latest update to Jet from the Microsoft website, I made the recommendation to download SP8. If people disagree with that. That's fine, its a free country. I have yet to see any documentation that would keep me from installing SP8.

Thanks,
Mike
Reply With Quote
  #10 (permalink)  
Old February 17th, 2004, 12:09 PM
Friend of Wrox
 
Join Date: Jul 2003
Location: Houston, Texas, USA.
Posts: 174
Thanks: 0
Thanked 0 Times in 0 Posts
Default

As I suggested previously, read the thread on "Sandbox Mode" and then the link provided regarding the macro issue. If you are only developing an app for internal use, then this probably won't affect you in the least. I on the other hand work for a software company and SP-8 is wreaking havoc amongst the development and deployment of our applications.

On another note, an individual asked me to assist with a relationship issue with their db. One table in particular took quite awhile to open. When it did, I saw why. There were over 100 fields, and 60 of them were memo fields. By normalizing the 'attendance' table, I was able to cut it down to 5 fields, that's all. It didn't even require another table. All I had to do was change the EmployeeNumber to Indexed Yes(Duplicates OK). This individual thought they could only have one row per employee and keep track of every date they missed.

Once I changed the table structure, it opened almost instantaneously. Not only that, then they were able to establish the 1 to many relationship which was needed.

So again, I restate a suggestion to rethink loading SP-8 *and* normalize the table.

Respectfully,

Beth M
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Array or Table Performance comparison bananas SQL Language 4 June 5th, 2007 05:29 AM
Performance prasanta2expert SQL Server 2000 6 December 15th, 2006 10:38 PM
what is the best to do, better performance alyeng2000 ASP.NET 1.0 and 1.1 Basics 1 December 13th, 2003 07:56 AM
Table performance rignhom SQL Server 2000 1 August 4th, 2003 06:23 PM



All times are GMT -4. The time now is 10:50 AM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.