My application needs to log data from 137 identical power supplies daily at a
certain time interval, into SQL Server database. What is the best possible design, especially in
terms of space usage?
Requires Free Membership to View
Best is a VERY relative term. I'm missing about 98% of your business requirements, so am only taking a VERY broad guess based on the small amount of information provided. Create a table with an ID (integer) and a description. This will be used as a codes table for each of the power supplies. Create another table with an ID (FK to the first table created), datetime and column for your parameters. Beyond that, it is impossible to suggest anything. You are basically asking for an optimal database design based on a single sentence. I would need a LOT of additional information to even begin to put something together that may meet your needs.
For More Information
- What do you think about this answer? E-mail us at editor@searchDatabase.com with your feedback.
- The Best Microsoft SQL Server Web Links: tips, tutorials, scripts, and more.
- The Best SQL Web Links
- Have a SQL Server tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical SQL Server questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
This was first published in February 2002
Join the conversationComment
Share
Comments
Results
Contribute to the conversation