Home > SI5 Documentation > User Guide > Pre-Implementation > Database and Server

Database and Server

Database and Server Requirements

Small LAN (multiple licenses of SI5)

Best:... Provide a dedicated server with backup capability to host the SI5 server databases.

Good:.. Provide a workstation with backup capability to host the SI5 server databases.  This machine would need to share files with all other SI5 users and stay online at all times while others are using any of the SI5 applications.

In each option above, the "SI5 Server" must be on the same domain or workgroup as all of the "SI5 Client" machines.



Data Architecture

SI5 operates in a distributed architecture.  Changes made to the Local Products Database stored on each SI5 Client computer are updated to the Server Products Database viaLANSyncat times to be determined by the user.  These changes are propagated to all users based on each user’s update strategy.  This means that you may at any time disconnect an individual user from the network since you will be using the local Master Table Database.  The next time the user connects; all changes will be propagated to the other users via the server.  The LANSync module keeps all product information in sync between the users.

LANSync also maintains the Server Projects Database which keeps track of all projects that are checked into the server.  All shared Projects are “checked-in” to the server.  To modify a Project it must first be “checked out” .  During checkout the Project is copied to the user’s local hard drive. Once checked out, the user may disconnect from the network and take the Project home or into the field.  Once the Project modifications are complete, the Project is checked back in to the LANSync server for possible editing by other users.  While the Project is “checked-out”, other users may view the Project and run reports, but no modifications are allowed.


Last modified


This page has no custom tags.


This page has no classifications.