Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Some suggestions (Score 1) 291

by Luminescence (#32846634) Attached to: Good Database Design Books?
This all really basic. A few million rows assuming the rows aren't really long is no problem for a home pc to handle. Some hints.

You have to make sure you aren't doing full table scans on any big table. Indexes are your friend.

Sql hasn't changed much in say, the last ten years. Newer books aren't going to help more than older ones.

The less joins the better without taking other things into consideration.

Duplicating data in tables is a bad idea. Not necessarily for performance reasons, but because every time you change that data you will have to remember to change it in more than one place.

There are other databases out there other than mssql and mysql that may improve your performance more than what you can change with schemas and sql querys.

Finally, if it is fast enough just leave it. There is a big difference between queries that get hit once a minute and a thousand times a second.

"Pay no attention to the man behind the curtain." -- The Wizard Of Oz

Working...