Follow

Project Repositories

Project Repositories

Your projects are stored in a project repository on a SQL Server or Azure SQL Database. When you open Discovery Hub for the first time, you can set up a repository in the Get Started wizard. If you do not, you will be prompted to set up a repository when you try to e.g. add a new project.

When you install a new version of Discovery Hub, you will be prompted to run an upgrade script that automatically updates the repository to ensure compatibility with the new software version.

Note: The repository settings are saved for the current user and installation of Discovery Hub. This means that if you open two instances of Discovery Hub and change the repository settings in one of them, you will change the repository settings for both.

Setting up a Project Repository

To change the repository settings, follow the steps below:

  1. On the Tools menu, click Options and then click the Project repository tab in the window that appears.
  2. In the Server name box, enter the name of the database server on which you want to store the project. Click the ellipsis (...) to choose one of the available servers in you local Active Directory, if any.
  3. In the Authentication list, click the mode of authentication you want to use. You have the following options:
    • Windows Authentication: Use the logged-in Windows user's credentials for authentication.
    • SQL Server Authentication: Use a login set up on the SQL Server. Enter the username and password in the corresponding fields.
    • Azure AD Password Authentication: Use Azure AD credentials from a domain that is not federated with Azure AD. Enter the username and password in the corresponding fields.
    • Azure AD Integrated Authentication: Use the logged-in Windows user's credentials for authentication, provided that he is logged in using Azure AD credentials from a domain that is federated with Azure AD.
  4. In the Database box, enter a name for the database, and then click Create to create a new database to use as repository. Alternatively, you can select an existing database from the list. If you enter the name of an existing, but empty, database in the box and click Create, Discovery Hub will offer to create the necessary tables and stored procedures in the database so it can be used as a repository.
  5. (Optional) In the Connection timeout box, enter the number of seconds to wait before terminating the attempt to connect to the server. The default is 15 seconds. A value of zero will disable the timeout.
  6. (Optional)In the Command timeout box, enter the number of seconds to wait before terminating the attempt to connect to the database. The default is 1800 seconds. A value of zero will disable the timeout.
  7. (Optional) In the Max. rows to copy field, enter the batch size when using ADO.net transfer. '0' equals unlimited.
  8. (Optional) In the Encrypt connection list, you can enable encryption of the connection, which is recommended when you are not in a private network (e.g. when your server is on Azure). You have the following options:
    • No: The communication is not encrypted (default).
    • Yes: The communication is encrypted. The server's certificate is verified by a certificate authority.
    • Yes, trust server certificate: The communication is encrypted. but the server's certificate is not verified. This setting is not recommended for use on public networks.
  9. (Optional) Enter a SSIS server name in the SSIS Server box.
  10. (Optional) Enter any addition connections settings in the Additional connection properties box.
  11. Click Test Connection to verify that the connection is working.
Was this article helpful?
0 out of 0 found this helpful

0 Comments

Please sign in to leave a comment.