If you are moving the ESHA Database from another installation, you can restore the database to your own instance. If you have Detached the database from a previous server, you can attach it to your own instance (see details below). If this is a new installation and do not have a copy of the ESHA Database already, contact ESHA support.
You will need to add user permissions to the database using Management Studio. You can use Windows authentication or SQL authentication.
Attaching the Database
Note: using the ESHA Database with your own instance of SQL Server will require the server collation to be 'SQL_Latin1_General_CP1_CI_AS'.
NOTE: The ESHA Database (eshadata) will be referenced as 'eshadata' in the remainder of this document. However, if you have renamed it, use the proper database name in its place.
To attach the SQL Database SQL Server 2012 or newer:
1. Check/change attributes on that file so it is not Read-Only.
2. Open Microsoft SQL Server Management Studio.
3. Connect to your server instance, and browse to Databases.
4. In the Object Explorer, right-click on 'Databases':
5. Choose Attach…
- Click Add…
- Browse to the location to which you copied the .mdf in step 1 above.
- Select the .mdf and click OK.
- Ensure the path to the .mdf and .ldf are correct.
- In the upper portion, note the Attach As setting. This should be the correct database name ('eshadata'). If it is incorrect, click in that box and edit.
- Owner should be 'sa'.
- Click OK.
6. After successfully attaching, change some properties of the database:
- Under Databases, right-click the 'eshadata' database, and choose Properties.
- In Properties, on the left click Options.
- On the right, locate 'Compatibility Level'. Change to the appropriate level (if different):
- SQL Server 2012: SQL Server 2012 (110)
- SQL Server 2014: SQL Server 2014(120)
- On the right, locate the Other option of 'Auto Close'. Set this to FALSE.
PERMISSIONS NOTE: After it has been attached you will need to assign permissions for any user that will access the data. Use SQL Server Management Studio to add the user's Windows Authentication (Active Directory user, or AD Group) to the role 'FPRole' that exists in the database. If you are not using Windows Authentication (Active Directory), refer to the Using SQL Authentication document for information.