Setting Database Permissions

After installing SQLExpress, SQL Server Management Studio and Aviation Safety ++ the database associated with the program can be connected to the server.

A security measure by Microsoft prevents data files from being copied with other than minimal permissions. For Aviation safety ++ to operate these permissions have to be changed.

The database files have been copied to a hidden directory on the computer's boot drive (C:) in a folder called 'ProgramData' .  Note that there is no space between the two words. By default the computer is not set to display hidden folders and files. To enable this feature follow the following procedure.

Enable Hidden Folders and Files

Open windows file explorer and click on the 'View' menu item.  Check the 'Hidden Items' check box. This will enabled hidden items to be displayed.

It is recommended that after setting the database files and connecting to the database that you uncheck the 'Hidden Items' check box so as not to accidentally delete a system file.

Navigate to the Database Files

Now that we can view hidden items navigate to the location of the database files. These files are named RiskControl.mdf and RiskControl_log.Idf.

They are located at following location C:\ProgramData\Dolby Software Solutions\

Set Database User Permissions

The following procedure needs to be completed on both the RiskControl.mdf and the RiskControl_log.idf files.

Right click on one of the two files and select 'Properties' (1st Image)

Select the 'Security' tab

Highlight the 'Users' Group. Note that the permissions are restricted to 'Read and Execute' and 'Read' . (2nd Image).

The User group permissions need to be 'Full Control' for this program.

Click Edit to change user permissions.

Referring to the 3rd Image highlight the Users (single click) and then tick the full control check box.

Click apply and then OK.

Repeat the above procedure for the other data file and then attach the files to the server.

Note: On some computers the 'Users' group may not appear and instead you may see a group called 'MSSQL$SQLEXPRESS' . If this group is shown and the USERS group is not then the above procedure is not applicable.