Results 1 to 5 of 5
  1. #1
    Join Date
    Nov 2012
    Posts
    5

    Unanswered: Data base design

    I'm looking for better data base architecture/design to insert the >800000 records for day.

    My requirement is

    There is a more then >500 sensors continuously send the data for every second(24/7). I need to collect the data from sensors,to be store in DB. for that,
    1.Need to create separate DB to store the collected data,
    2.Need to be take the back up for every 1-2 minute for the stored data,
    3.Need to create the separate table for Reporting,issues etc
    4.I need to create separate DB for alerts like if captured temperature from the sensor is >50 deg then store data in normal dB or if <50 store in other DB.

    Please suggest the better architecture to design the DB

    Please give the better architecture to design DB.

  2. #2
    Join Date
    Oct 2009
    Location
    221B Baker St.
    Posts
    486
    Better than what? You have posted nothing for us to try to do better than.

    Is the data collection process from the sensor already working? How is the data presented to your processing?

    How often do you believe you need to "create separate DB" or is this a one-time process?
    Last edited by papadi; 11-18-12 at 00:17.

  3. #3
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    What is your current design, and what are the problems you're having with it?

    How do you cope with the problems in your specifications? My guess would be that those flaws are the root of your performance problems, but without any insight into what is broken I have no way to help you fix it.

    -PatP
    In theory, theory and practice are identical. In practice, theory and practice are unrelated.

  4. #4
    Join Date
    Nov 2012
    Posts
    5
    Dear Papadi,Pat Phelan

    Thanks for your reply....!!!

    Please find my comments below,

    1. As of now i could not design the any architecture for this and I'm looking for the most efficient and less time consume design for insertion and selection.

    Is the data collection process from the sensor already working? How is the data presented to your processing?

    2. Yes it is working and data base table as to be like below

    Cloumn1 - int - NotNull - Primary Key
    Cloumn2 - nVarchar(1000) - NotNull
    Cloumn3 - int - Null
    Cloumn4 - int - NotNull
    Cloumn5 - Datetime - Null
    Cloumn6 - int - NotNull - Foreign Key
    Cloumn7 - int - Null
    Cloumn8 - Varchar(50) - NotNull
    Cloumn9 - Varchar(50) - NotNull

    3. How often do you believe you need to "create separate DB" or is this a one-time process?

    Yes, it is a one time process.

  5. #5
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    Quote Originally Posted by sureshkallem View Post
    1.Need to create separate DB to store the collected data,
    OK

    Quote Originally Posted by sureshkallem View Post
    2.Need to be take the back up for every 1-2 minute for the stored data,
    No, you just need your database to be in full recovery mode. You can do point-in-time recovery from the log if that becomes necessary.

    Quote Originally Posted by sureshkallem View Post
    3.Need to create the separate table for Reporting,issues etc
    You'll probably need to create several. They can be in the same database.

    Quote Originally Posted by sureshkallem View Post
    4.I need to create separate DB for alerts like if captured temperature from the sensor is >50 deg then store data in normal dB or if <50 store in other DB.
    No, you just need separate tables for this. They can all be in the same database as the collected data.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •