Best way to design database structure for storing equipment dynamically
-
Monday, December 03, 2012 4:46 PMI'm wanting to design a database to store equipment in a system related to an client as the master table. So far there is about 20 differnet pieces of equipment with different values to be stored in columns that are unique to each piece of equipment. I started by creating a table for each kind of equipment but was wondering if there is to create one table to store each piece of equipments fields that need to be captured and data type for that field. The trick also would be reporting on this data later on down the line if it is dynamica like this. Any help is appreciated.
Michael Duhon
All Replies
-
Thursday, December 06, 2012 6:39 AMModerator
Hi Michael,
Designing a database requires an understanding of the business functions you want to model. It also requires an understanding of the database concepts and features that you want to use to represent those business functions. Make sure that you accurately design the database to model the business, because it can be time-consuming to significantly change the design of a database after you implement it. Please refer to:
http://msdn.microsoft.com/en-us/library/ms187099(v=sql.105).aspx
http://www.simple-talk.com/sql/database-administration/ten-common-database-design-mistakes/
Thanks,
Eileen
If you have any feedback on our support, please click hereEileen Zhao
TechNet Community Support
- Marked As Answer by Eileen ZhaoMicrosoft Contingent Staff, Moderator Wednesday, December 12, 2012 1:03 AM
.png)
