(panabong@gmail.com) writes:
> Basically, i have equipment which is sending me a lot of gauges
> readings (high limit, low limit, current level), electrical readings,
> hydraulic readings, alarms levels such as Fuel level, temperature
> level, etc etc, about 200 different types of readings, continuously. I
> may have different types of equipments and although most of the data
> are the same, except some data types and its availability may be
> different., depending on the type of equipment.
>
> I want to keep this readings in a database, and this database will be
> updated constantly. I will update display using the readings from the
> DB. Eventually i also want to use the data from the database to plot
> chart or run simulation.
>
> Should i create all of this different gauges readings in one big
> single table? If i do so, i only have one long row of data then for a
> particular equipment.If i put in different table, i can't see how i
> can create relationship among my tables with such kind of data.
>
> Can you on the possible ways of putting this equipment real time
> readings into DB?

One alternative is have one row for each reading. That makes it easier
to deal with if the values can come in different frequencies, as
each row also could have a timestamp go with it. I assume that you keep
some history of th readings. Then again, if the values from different
domains, this can be messy.

But I really know too little of your requirements and your system to
be able to say anything authorative.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx