Follow

Attaching the Database to your instance of SQL Server 2008 R2 or newer

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 (gendata for Genesis, eshadata for Food Processor) will be referenced as 'gendata' in the remainder of this document.  However, if you have renamed it, or are using Food Processor, use the proper database name in its place.

To attach the SQL Database SQL Server 2008 R2 or newer:

1. Check/change attributes on that file so it is not Read-Only.

2. Open Microsoft SQL Server Management Studio (Express or full, whatever you have).

3. Connect to your server instance, and browse to Databases.

4. In the Object Explorer, right-click on 'Databases':

5. Choose Attach…

  1. Click Add…
  2. Browse to the location to which you copied the .mdf in step 1 above.
  3. Select the .mdf and click OK.
  4. Highlight 'gendata_log.ldf' from the list in the lower right. (eshadata_log.ldf for Food Processor)
  5. Click Remove to remove the log file from the list.
  6. In the upper portion, note the Attach As setting.This should be
    'gendata'. If it is anything other than 'gendata', click in that box and edit it to read 'gendata'. (Again, for Food Processor, replace gendata with eshadata)
  7. Owner should be 'sa'.
  8. Click OK.

6. After successfully attaching, change the Compatibility Level to the proper value for your SQL Server instance:

  1. Under Databases, right-click the 'gendata' database, and choose Properties.
  2. In Properties, on the left click Options.
  3. On the right, for Compatibility Level, change to the appropriate level (if different):
    • SQL Server 2008: SQL Server 2008 (100)
    • SQL Server 2012: SQL Server 2012 (110)
    • SQL Server 2014: SQL Server 2014(120)

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.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk