CivilPro can operate as either a standalone (file based) system on a local computer, or as a server install (SQL Server) networked between multiple users. You need to decide which kind you are going to use right at the start, so a little bit about each is below. There is no difference in the use of Civil Pro once the database is set up.
If a standalone system suits your needs, it is by far the simplest and if you need to change to a server based system later, Civil Pro will migrate your standalone file to a server in a matter of minutes.
A standalone database stores all of its information in a single file which is saved locally on your computer or a network share. You can still create as many projects as you like in a single file.
- Simple to administer
- Backup by making a copy of the database
- Easily archived
- Very little multi-user capability
- Slower with large projects
- No server based automation of backup processes and data recovery
A server install can be set up on a single machine. It does not need to be a server computer. The term server refers to the technology – being a database server. You can run CivilPro’s client application and a Microsoft SQL Server Express easily on a modern computer.
Of course, if you have a company wide system or many users, you will want the database to run on a central machine with reasonable specifications.
Backups, restores and administration are all server-based tasks requiring either a reliable backup of the environment in which the server is running, or someone who knows about using a database server. If you need to use your project where you cannot access the server, you can temporarily convert it to a standalone file and back again.
- Essential for multi-user environments
- Data can be aggregated across projects
- Central control of all data and backup processes
- Stronger access control
- Can be inexpensively achieved using MS SQL Express (free)
- Requires basic SQL server knowledge by IT department or user
- Data transfer requires standard database backup/restore