Static/Singleton Class for Global Hash Table?

I have a database table with 600 rows, that looks something like this

[ These Are Natural Key ]
Car		Part		MyDescription
char(64)	char(64)	char(256)
---		----		------------------------------------
Honda		Tire		Looks like a donut, but not as tasty
Honda		Wheel		Shiny and wears a rubber shoe
Ford		Engine		Eats gas and makes loud noise.
Chevy		Tire		Donutish but not for a Honda.

Open in new window

It's not actually car parts of course.



I need to load the entire 600 rows into memory when the user starts their app. Frequently other classes will need to return a single Description (Field3) FAST when given a Cart.Part (Field1, Field2) composite natural key. Nothing else, no sorting, lists, updating, for-each loops, just speed.

Many times in the code I'd like to do retrieve the Description (Field3) roughly like this?

string MyDescription = MyNewExpertclass.Get("Honda.Tire");


I'm a database guy mostly. It seems a Hash Table would be perfect since I know the size beforehand and don't need to update, order or loop through the data.  

Singleton doesn't seem correct, but maybe a static object containing the hash table so that it is loaded once and accessed many times throughout the application code?
EZSundayAMAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

käµfm³d 👽Commented:
Is the program multi-threaded?
0
käµfm³d 👽Commented:
Actually, disregard my last question. If the collection will be read-only, there shouldn't be any threading issues--provided you load it fully before you start reading it.

I believe a static object would suit your purposes. Singleton ensures that only one instance of a class is in existence during the life of the application. For this purpose, I think you will achieve the same functionality using a static object.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
EZSundayAMAuthor Commented:
Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
C#

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.