I am working on an application which will record around 95Million records per year. Now I am trying to find out how the data needs to be stored to achieve best performance. I was thinking instead of pushing 95Million records in the same table to create a db for every month and then a table per day. that way there are only about 280k entries per table. data is not alot. there are only 8 columns per table and data from one day does not need to be compared with data of another day. Does the above make sense?
I think that is not a problem to store them. In any case your problem will be streaming and downloading such data from the server.
MySQL can handle a table that size. Just make sure you index on what you need to find. A linear search through a table that size is something you start when you go home on Friday if you need the results on Monday. (And remember, "LIKE" is a linear search.)
you can use microsoft sql to store data. list out all the data types you would like to store create a table using create table command u can also read Relational database concepts to understand better
You say you want to store data to get the best performance. That is meaningless. Best performance doing WHAT? Adding records? Deleting records? Updating records? Accessing records? Or what? What do you mean by best performance? How are you using the collected data? How are you accessing it?