If this is your first visit, be sure to check out the FAQ by clicking the link above.
You may have to register before you can post: click the register link above to proceed.
To start viewing messages, select the forum that you want to visit from the selection below.
I solve following problem. I have 10 000 users and every user send to database 30 data segments (one segment = 1 byte) per minute. I need also using search. I have no idea what database scheme is best to save this data. Can you help me please? I use MSSQL 2005 server.
Not always. Number of segments can be less or greater than 30 segments.
Segment is ONE byte - etc. 30 segments is packet whose size is 30B (I selected bad convention ... sorry ) Segment is simply one byte.
I am storing results of health measurement etc. ecg, heartbeat.
So you don't know all the measurements that may be taken (heartbeat, etc)?
Will data be received as complete packets, or will inserts/updates be made on individual segments?
This is a tough call, but based upon your data volume and search requirements, I'd recommend one record per packet, with 30+ columns to cover each segment.
__________________
If it's not practically useful, then it's practically useless.