Network Installation Instructions - ESTIMATION

Instructions for preparing the installation

1. I need to connect to this server to install ESTIMATION.  If the client does not have access to RDP, I connect with Screen connect

2. To be able to use Screen Connect ports 8040 and 8041 are used by default.

3. Create a user to allow me to run the SQL services and execute a scheduled task that I will create (for the backup of bd).

4. Create a group on the domain for ESTIMATION users (CBE) and associate the users who will use the software.  This group will be used to access SQL and the shared folder on the network.

5. Tell me where to put the shared files (read and write) for the program. (Example : X:\CBE root\ or \Server root\ )

6. Additional information to know

   1. On the server we install

      1. Microsoft SQL Server Express 2016

      2. ConstructionBuy Server Estimate

      3. Expertisa Client (Usually in C:\Program Files)
         

   2. On the server you must create a backup of the following directories:

      1. \\Server\CBE Root\

7. To serve you well we strongly recommend having an RDP connection to be able to connect to a server having access to ESTIMATION

   1. Create a user: ESTIMATION Admin (having access to the server where ESTIMATION Server is installed)

Database configuration

At installation, we create 3 scheduled tasks to do the maintenance and backup of the databases.  This allows the customer to tailor this maintenance to meet their specific needs.

Database backup

We offer the customer the possibility to back up according to 2 recovery models: the Simple recovery model and the Full recovery model. The customer can choose either one to meet his needs.

Simple recovery model

It allows you to restore the database at a point planned in advance.  For example, if I make a backup every morning at 7:00 am.  I will be able to restore my database at these precise moments when I made a backup.

The program executed to meet this need is "ExecMaintenance.cmd" with the parameter "ExpertisaDailyBackup.sql"

Edit the file to fit your needs:

@Databases = 'Expertisa%', -- This variable indicates the databases to be backed up.  In this case, we save all the databases starting with Expertisa.  We could also write 'Expertisa, Expertisa_Config' to backup only these 2 databases.@BackupType = 'FULL', - This indicates that we are doing a full backup - @Verify = 'Y', - Verify the integrity of the backup after the operation.@LogToTable = 'Y', -- Write a log of the operations performed in the database.@CleanupTime = 360 -- How long (in hours) to keep the backups in the backup directory before deleting them. (Automatic rotation of the backups)--,@Directory = 'C:\Backup' - If you want to save in another directory than the default one, you can indicate another path.  This parameter is not mandatory. -- You can also save to multiple locations.  Here is how the syntax would be: @Directory = '\Server1\Backup, \Server2\Backup, C:\Backup'

Sharepoint directories do not seem to work.

What works

Dropbox : yes

Google Drive: yes

OneDrive:?

Full recovery model

This model allows you to restore the database at any moment in time.

In order to do this, you need to run "ExecMaintenance.cmd" with the parameter "ExpertisaDailyBackup.sql" and you also need to run "ExecMaintenance.cmd" with the parameter "ExpertisaHourlyBackup.sql"

This has the effect of saving the "Transaction Logs" (by default, every hour), which allow restoring the DB at any point in time.

The ExpertisaHourlyBackup.sql file includes these parameters:@Databases = 'Expertisa%', -- Database to be taken as a backup.  Note that the database must be in full recovery mode for this backup to take place, -- See other comments in the simple recovery.
@BackupType = 'LOG', -- This indicates that only Transaction Logs are backed up.@LogToTable = 'Y', -- Write a log of the operations performed in the DB.@CleanupTime = 360 -- How long (in hours) to keep the backups in the backup directory before deleting them. (Automatic rotation of the backups)-- ,@Directory = 'C:\Backup' -- See comments in the simple recovery.

The maintenance system

A task is also created to do maintenance on the databases.  More precisely: 1-The indexes are recompiled, 2- the SQL server plans are redone to optimize the queries

In order to do this, you need to run "ExecMaintenance.cmd" with the parameter "ExpertisaIndexAndStatsMaintenance.sql".