SkySync can be configured to use either the default SQL CE database (installed with SkySync's installer using "Typical Installation"), SQL Server database, or SQL Server Express database. In scenarios where SkySync will be tracking large numbers of items and/or performing large numbers of jobs, using a SQL Server or SQL Server Express database will provide enhanced performance over SQL CE. The job auditing feature, which allows for full auditing of all changes made by SkySync, also requires SQL Server or SQL Server Express due to the database size required to track every operation.
Creating a database through SQL Management Studio
In order to configure SkySync to use SQL Server or SQL Server Express, the database must be created prior to installation. Additionally, SkySync will need to connect to this database with read and write privileges using either NTLM or SQL Authentication. It is highly recommended that a service account is used to make this connection.
Open SQL Server Management Studio, right-click Databases in the Object Explorer, and select "New Database".
Name the database and select an owner. The owner can be the SkySync service account mentioned above, or follow the security standards for your organization.
Once the database is created, follow the process outlined in the section below titled “SQL Server (Custom Installation)” to point the SkySync install to this database.
SQL Server CE (Typical Installation)
Selecting a typical installation will install SkySync configured for SQL Server CE. The database will be created automatically as part of the install.
SQL Server (Custom Installation)
Run the SkySync installer and select Custom installation. You will be prompted to define the installation and ProgramData paths.
The next screen is where you configure what account the SkySync Service will use to log-in as. Select the "This account" radio button and enter in the credentials for an account with access to all of the network resources that will be synced. Our best practice recommendation would be to have this account separate from the SQL Connection Account.
Next you will be asked to configure any proxy server settings.
Next is the Database Configuration screen. Click on the drop-down menu and select "SQL Server" to reveal the configuration fields.
Enter in the Server Name where the database is located, the correct port number, and the name of the database created in SQL Management Studio. Leaving blank will default to the standard SQL Communications port 1433.
If using Windows Authentication check the appropriate box. Otherwise enter in the credentials for the owner account of the SQL database.
Click "Validate" to verify the account. The SkySync installer with automatically build the connection string to the database. Click on the Advanced link under the Database field to expand the Connection String field, displaying the automatically generated string. Manually entering a connections string is not required for completing the installation of SkySync configured to use SQL Server.
Click "Next" to proceed to the "Confirm Configuration" screen where you can review all install options and begin the installation.
Moving from SQL Server CE to SQL Server or SQL Server Express
If you currently have SkySync installed using SQL Server CE and wish to move to using SQL Server or SQL Server Express, there are two options:
- Simply uninstall SkySync and run the installer, following the custom installation steps above. This will cause the loss of your currently configured jobs and their histories. As you recreate your old jobs, make sure to select the “Use Trust Mode” checkbox under Advanced in the Add New Job screen. With this selected, when the job runs the first time after being recreated, SkySync will “trust” that files that exist on both sides are equal, and will not be transferred. Please note this setting only applies for the first time a job is run.
- If you wish to preserve your current jobs and job histories, the database will need to be migrated with the assistance of one of our engineers. This process typically takes one to two hours depending on the size of the database. Please contact Portal Architects Support to schedule a time for this process.
Please contact Portal Architects Support for assistance with this article.