Welcome to the dBforums forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

If you prefer not to see double-underlined words and corresponding ads, place your cursor
here for ContentLink opt out.

Go Back  dBforums > General > Database Concepts & Design > DB Scheme for small data segments

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 10-08-07, 15:05
Veolw Veolw is offline
Registered User
 
Join Date: Oct 2007
Posts: 4
DB Scheme for small data segments

Hi all,

first sorry for my bad English

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.

Thank you very much.
Reply With Quote
  #2 (permalink)  
Old 10-08-07, 15:48
blindman blindman is offline
World Class Flame Warrior
 
Join Date: Jun 2003
Location: Ohio
Posts: 9,291
Always 30 segments? Are there sometimes less than 30 segments? Is there any possibility that there could be more than 30 segments?

What is a "segment", and what kind of data are you storing?
__________________
If it's not practically useful, then it's practically useless.

blindman
http://sqlblindman.googlepages.com/main
Reply With Quote
  #3 (permalink)  
Old 10-08-07, 17:19
Veolw Veolw is offline
Registered User
 
Join Date: Oct 2007
Posts: 4
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.
Reply With Quote
  #4 (permalink)  
Old 10-08-07, 17:43
blindman blindman is offline
World Class Flame Warrior
 
Join Date: Jun 2003
Location: Ohio
Posts: 9,291
Do you need to search for individual segments, or just by person?
__________________
If it's not practically useful, then it's practically useless.

blindman
http://sqlblindman.googlepages.com/main
Reply With Quote
  #5 (permalink)  
Old 10-09-07, 10:46
Veolw Veolw is offline
Registered User
 
Join Date: Oct 2007
Posts: 4
Both. I want search for individual segments and by person too.
Reply With Quote
  #6 (permalink)  
Old 10-09-07, 12:19
blindman blindman is offline
World Class Flame Warrior
 
Join Date: Jun 2003
Location: Ohio
Posts: 9,291
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.

blindman
http://sqlblindman.googlepages.com/main
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On