Multi-use SQL Server

  • Hi;

    Just wanted to see if anyone has real world experience in the manufacturing sector and more precisly, mixing manufacturing plant-floor data on the same physical server as administration data in a large multi-site enterprise system.

    It is my intent that all plant floor systems read and write data to a desktop DB and have replication propagate changes to the server. My fear is the shear volume of transactions from the plant floor not only having a deleterious affect on the server but also the WAN.

    Would there be any benefit of each site maintaining its own db server and propagating changes during off hours. Any benifit of isolating the Admin and plant floor servers entirely.

    Thank you for your assistance.

  • What kind of volume are we talking about? I assume you would be using access or MSDE for the desktop yes?

    Wes

  • Because it's a manufacturing environment the volume may be quite high. Manufacturing data volume changes on a daily bases as lines are added, discontinued, on-line, off-line. The rows themselves are usually fairly small...perhaps 5 columns of ints and reals, but a transaction could contain 5 - 1000 rows.

    1 operator station could produce 3 transactions per minute.

    Some stations transmit 1 transaction every 15 minutes.

    It is unclear how many stations could be present in the near future, at the moment there are 7 stations.

    MSDE will be used for the desktop. Merge Replication would probably be used accross the facility to allow for near real-time analysis.

  • If it is such a small amount have you tried direct connections to the database and only logging localy if the connection isn't available? A few thousand transactions shouldn't be that big a deal. If that isn't an option just setup a DTS job to handle all the imports for you.

    Wes

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply