I have an application that does the following.
A UDP packet comes into the server with say 5 pieces of data (5 varies widely) and the receive program creates an entry in a table we'll call 'packet'.The entry looks like:
[ProductID] [Timestamp] [PacketID] - [PacketID] is primary key
Then each piece of data is inserted into a table we'll call 'productresults' and looks like so:
[PacketID] [Value] [id] - [id] is primary key
so in this instance the packet record tells us the productid and timestamp for each of the 5 pieces of data (remember 5 can be 1 - 100 it varies by product)
Was this the best way to store this?
We can have hundreds of products, should I have 1 table for all results or should I have a seperate table for all resulting in hundreds of tables?
Any advice is highly appreciated.
A UDP packet comes into the server with say 5 pieces of data (5 varies widely) and the receive program creates an entry in a table we'll call 'packet'.The entry looks like:
[ProductID] [Timestamp] [PacketID] - [PacketID] is primary key
Then each piece of data is inserted into a table we'll call 'productresults' and looks like so:
[PacketID] [Value] [id] - [id] is primary key
so in this instance the packet record tells us the productid and timestamp for each of the 5 pieces of data (remember 5 can be 1 - 100 it varies by product)
Was this the best way to store this?
We can have hundreds of products, should I have 1 table for all results or should I have a seperate table for all resulting in hundreds of tables?
Any advice is highly appreciated.