Re: [MS_AccessPros] Looking for Access performance suggestions

 

primary keys is not necessary for AutoNumbers -- just unique index

On 12/4/2018 3:54 PM, crystal 8 wrote:

hi Brooks,

I would suggest adding AutoNumber primary keys (with unique index) and Long Integer Foreign keys (default value=Null, index that allows duplicates and ignores null) with a set of queries to update the foreign keys. Then use the Long Integers to link. Add fields to the end if you import and other fields need to be in a certain order. This will greatly enhance performance.

Size:
AutoNumber/Long Integer = 4 byte
2 dates, a long number and a 1 character text fields = 2*8 + 4 + ? --> more than 20

So just by doing this, each join will be at least 5 times faster. The indexes will help speed it up too.

~crystal

On 12/4/2018 3:14 PM, brooksrimes@bigfoot.com [MS_Access_Professionals] wrote:

Hi Crystal,

Thanks for the post.

Unfortunately, the 3 million row tables needs 4 fields for the primary key: 2 dates, a long number and a 1 character text fields.

The frontend and backend are both on my Dell laptop with a Intel Core i5 processor and 8 GB of RAM.  I just upgraded from a HDD to a SSD and there was only a 9% reduction in run time.  

I compact and repair regularly.  I've been using Access since 1.0.  

A separate database server running SQL Server is probably an option.

Brooks

__._,_.___

---

Posted by: crystal 8 <strive4peace2008@yahoo.com>

---

Reply via web post

•

Reply to sender

•

Reply to group

•

Start a New Topic

•

Messages in this topic (5)

---

Have you tried the highest rated email app?

With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.

---

Visit Your Group

• Privacy • Unsubscribe • Terms of Use

SPONSORED LINKS

.

__,_._,___