Search the Knowledgebase Browse by Category
Attaching the Genesis R&D SQL Database to your instance of SQL Server 2005 or 2008
User Opinions
100% thumbs up 0% thumbs down (6 votes)

How would you rate this answer?
Helpful
Not helpful
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'.

To attach the Genesis R&D SQL Database (gendata) in SQL Server 2005 or 2008:

1. Copy the gendata.mdf file from "[CD]:\win32\program files\ESHA Research\data" into a drive that is local to the server (recommended is "c:\program files\ESHA Research\data").

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

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

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

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

6. 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.
  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'.
  7. Owner should be 'sa'.
  8. Click OK.

7. 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 from SQL Server 2000 (80) to:
    • SQL Server 2005: SQL Server 2005 (90)
    • SQL Server 2008: SQL Server 2008 (100)

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.

Attachments
No attachments were found.
Related Questions

Powered by ActiveKB Knowledgebase Software