On Mar 26, 10:43am, panab...@gmail.com wrote:
> Hi,
>
> I need to design a database, but i i just don know if i am doing it
> correctly.
>
> 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?

You don't necessarily have to have a relational database, it is just
useful for data integrity. You could have one table per piece of
equipment if that makes sense. If you started repeating data, that
would be a prompt to pull it out and make a related table.