Applies to: @RISK Professional and Industrial Editions, 6.2 and Up

Issue:

When following the procedure in SQL for @RISK Library on Another Computer:

1. Not getting a list of databases.
2. Nothing happens when creating a database

Solutions:

1. Verify that you have SQL Native Client or SQL Server installed.
   1. See SQL Versions and Installation.
2. Try making a dummy connection to test connectivity, user names, and passwords outside of the @RISK context.

Verifying SQL Server Connectivity via ODBC

This procedure is written for Windows 7, but is similar on other Windows versions. Any errors or unexpected behavior are not related to @RISK. Your IT person should help resolve these issues and verify that you have both a Windows login and an SQL login on the remote computer.

Steps:

1. 1. Open Control Panel → Administrative Tools → Data Sources (ODBC).

   2. On the ODBC Data Source Administrator screen, click Add, select SQL Server, and click Finish.

   3. Enter a dummy name and description, pick your remote SQL server from the list, and click Next.

   4. On the next screen, check "Connect to SQL Server to obtain default settings". Enter your login credentials. (Your IT person can advise whether to use Microsoft Authentication or SQL Authentication.) Click Next.

   5. On the following screen, check "Change the default database to", select a database from the list, and clear the "Attach database filename" box. Click Next.

   6. Click Finish.

Note: You don’t need to keep this dummy data source permanently. Once connectivity and authentication are verified, use the same credentials on the @RISK Library screens, then remove the dummy data source from the ODBC Data Source Administrator.

Related Article: @RISK: Library Can't Find SQL Servers on Other Computers