MySQL Forums
Forum List  »  Partitioning

PARTITION or sEPERATE tABLE ISSUE
Posted by: hrishi patil
Date: October 29, 2009 06:32AM

HI,
I am designing database for fleet management system.
I will be getting n numbers of records every 3 seconds.so obviously there will be millions of record in my table (where I am going to store current Information of vehicle in current_location table) .Here performance is an BIG issue.
So to solve this I got an an following suggestion.
1>Create an septate table for each vehicle.
Here a table will be created at a run time as as soon as I click on create new table.And all the data releted to perticular table will be inserted and retrive from that perticular table
2>Go for partition

CAn u please tell me
1>whwt is difference between this abhove points.(partition/ create table when at run time recqured and put all relevent data AND Sharding)
2>which is best.And Why
3>My sencere question
Till what number of record my performance wont get heated .There may be something that till 50000 or something number of record my sql operate well and after that it performance is heated.
4>Any other solution

I am using ASP.NET with my sql.

Options: ReplyQuote


Subject
Views
Written By
Posted
PARTITION or sEPERATE tABLE ISSUE
3361
October 29, 2009 06:32AM
2139
October 30, 2009 09:35AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.