Palisade Knowledge Base

HomeTechniques and Tips@RISK: General QuestionsSQL for @RISK Library on Another Computer

2.8. SQL for @RISK Library on Another Computer

Applies to: @RISK Professional and Industrial Editions, releases 6.2, 6.3, and 7.x

Do I need SQL on my computer to read and write @RISK libraries on other computers?

Yes, the @RISK Library on the local computer needs compatible SQL software to talk to the remote database. If you're not storing @RISK Library databases on your local computer, you could use SQL Native Client or SQL Server to access the remote databases. A computer that hosts an @RISK Library database needs SQL Server, and it must be running a Server version of Windows. Please see SQL Versions and Installation: SQL with @RISK 6.2 and later for more.

Connecting to an existing database on a remote computer:

  1. Make the appropriate selection to open the @RISK Library window:

    • In Define Distribution, click the books icon, "Add Input to Library".
    • After a simulation, in the ribbon click Library » Add Results to Library.
    • If you want to access existing library entries rather than add new ones, in the ribbon click Library » Show @RISK Library.
  2. Once in the @RISK Library window, click the books icon near the middle of the screen. The icon displays "Connect, Create, or Attach to Databases" if you hover your mouse over it.

  3. Click Connect.

  4. On the SQL Connection screen, select an authentication method. "Microsoft Authentication" means your standard Windows login will be used; this is correct for most users. If necessary, change to "SQL Server Authentication" and enter your user name and password.

  5. @RISK will search your network for installed SQL servers; this can take some time.  The list includes all computers with SQL server software installed, whether they actually have any databases or not.

  6. When the list appears, click the name of the computer where you want to access an @RISK Library database. @RISK will then query that server for available databases.

    If no databases appear, either none exist on that server, you don't have privilege to access them, or you didn't specify the correct user name and password. Please see Library Can't Connect to Networked Database for troubleshooting.

  7. Select the desired database and click Connect. The database will be added to your list of Current SQL Server Connections, and @RISK will remember the connection next time.

Creating a new database on a remote computer:

  1. Make the appropriate selection to open the @RISK Library window:

    • In Define Distribution, click the books icon, "Add Input to Library".
    • After a simulation, in the ribbon click Library » Add Results to Library.
  2. Once in the @RISK Library window, click the books icon near the middle of the screen.  The icon displays "Connect, Create, or Attach to Databases" if you hover your mouse over it.

  3. Click Create.

  4. On the SQL Connection screen, select an authentication method. "Microsoft Authentication" means your standard Windows login will be used; this is correct for most users.  If necessary, change to "SQL Server Authentication" and enter your user name and password.

  5. @RISK will search your network for installed SQL servers; this can take some time.

  6. When the list appears, click the name of the computer where you want to create an @RISK Library database.

  7. Type a database name and click Create. The database will be added to your list of Current SQL Server Connections, and @RISK will remember the connection next time.

    If the screen closes when you click Create, but the new database is not shown on the Current SQL Server Connections screen, it was not created. Either you don't have the necessary access rights on that computer, or you didn't enter the correct authentication information. Please see Library Can't Connect to Networked Database for troubleshooting.

See also: "Library" in the Guided Tour of @RISK is a short video that shows you how to save distributions and results in a library and how to make use of them in your model.

Last edited: 2015-03-26

This page was: Helpful | Not Helpful