Toad allows you to create a native Snowflake connection, which provides you with a full-featured Object Explorer, Query Builder and SQL Editor.
Note: You must have a Snowflake ODBC driver 2.24.2 (or later) installed before a native connection is created.
To install the Snowflake ODBC Driver
Download and install the ODBC Driver from the Snowflake Web site.
Click 
Enter the connection information in the Create New Connection dialog. Review the following for additional information:
Review the following for additional information:
| General Tab | Description |
|
Host |
Enter the name of the server hosting the database to which you want to connect. |
|
Authentication |
There are four types of authentication that you can use to connect to Snowflake in Toad. The required Login fields will change according to the type of authentication you select. All the authenticators are located in a dropdown list:
|
|
User |
Enter the username for your Snowflake account |
|
Password |
Enter the password for your Snowflake account |
|
Token |
Enter your authentication token (Only visible when connecting via OAuth) |
|
Private key path |
Enter your Private key (Only visible when connecting via Key pair) |
|
Passphrase |
Passphrase is required only if the keys are encrypted (Only visible when connecting via Key pair) |
|
Port |
The default port number for Snowflake is 443 |
|
Optional |
A connection can be made without providing this information |
|
Role |
Enter the user role that you would like to connect to |
|
Warehouse |
Enter the name of the Warehouse you would like to connect to |
|
Database |
Enter the name of the Database(s) you would like to connect to |
|
Schema |
Enter the name of the Schema(s) you would like to connect to |
Click Connect to save the connection and immediately connect to the database.
or
Click Save to save the connection without connecting to the database.
When using SSO or MFA, there is a way to maintain continuous and secure connectivity without needing to enter login credentials for each connection attempt to Snowflake (as well as to prevent additional browser loading whenever a new module is started in Toad Data Studio). To achieve this, check whether the correct parameters have been set in your account by executing the query below in your Snowflake cloud interface:
SHOW PARAMETERS IN ACCOUNT;
The output that will secure login credentials caching will have these values:
For SSO
allow_id_token = true;
For MFA
allow_client_mfa_caching = true;
If these values are set to false, then the following queries need to be executed:
For SSO:
ALTER ACCOUNT
SET allow_id_token = true;
For MFA:
ALTER ACCOUNT
SET allow_client_mfa_caching = true;
Note: If a Role or Warehouse isn’t chosen, the default settings from the Snowflake User account will be applied (it is considered best practice that a user sets a default Role and a default Warehouse in their Snowflake user account).
Tip: It is strongly advised to use only the Snowflake user account authentication when creating Automation scripts to avoid unnecessary workflow interruptions.
Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help | About.
Troubleshoot SQL Server® Issues
You can create a new connection, or connect to an existing connection from the Create New Connection window. See Troubleshoot SQL Server® Issues for more information about troubleshooting connection issues.
Note: For SQL Azure connections:
Click
Select Microsoft SQL Server or Microsoft SQL Azure from the Group list box.
Review the following for additional information:
| Login Tab | Description |
|
Server name |
Enter the name of the server to use when connecting. Click Notes:
|
|
Authentication |
Select the type of authentication to use for this connection.
Note: You cannot create a SQL Azure connection using Windows Authentication. |
|
Password |
Enter the password to use when connecting. Tip: After connecting, you can set a master password to further secure your connection in Tools | Options| Environment | Security. |
|
Application ID |
Enter the application ID located in App registrations in Azure Active Directory. (This is a mandatory field when connecting to Microsoft SQL Azure via MFA.) |
|
Redirect URI |
Enter the appropriate redirect URI.(This is an optional field when connecting to Microsoft SQL Auzre via MFA which can be left empty unless you have specific requirements for configuring the Redirect URI.) |
|
Category |
Select or create a category if you want to color code Editor tabs for a specific connection. This can help differentiate between development and production databases. You can also set an option to color code the Object Explorer pane and object editor windows (Create, Alter, Drop, etc.). |
|
Encrypt connection |
Select this option to enable encryption for the current connection provided that the certificate has been already installed on the server. |
| Advanced Tab | Description |
|
Network protocol |
Select one of the following:
|
|
Parameter Name/Value |
You can add parameters to the connection. Toad includes the Application Name parameter with value Toad Data Studio by default. |
|
OBDC driver |
Select an ODBC driver to use for this connection when creating cross-connection queries. Tip: You can specify the ODBC driver to use for all connections for this database provider in Tools | Options | Database | SQL Server. |
Click Connect to save the connection and immediately connect to the database.
or
Click Save to save the connection without connecting to the database.
Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help | About.
To import connections (including Central Management Server connections)
.
Specify the location where the connections currently reside.
Note: Review the following for additional information on CMS connections:
Troubleshoot SQL Server® Issues
To create this type of connection to Microsoft SQL Azure, Active Directory Universal with MFA needs to be selected from the Authentication field dropdown.
The next step is to enter a user name which has been configured for multi-factor authentication and put in the appropriate App ID. After filling out the required information, click on Connect.
The step that follows will enable you to select a user from the list or add another one by clicking on Use another account.
After that, you will be prompted to enter your credentials and depending on the type of authentication that the account has been configured with, you will undergo an additional authentication step, such as the one in the image below.
After completing the final authentication step, a successful connection to Microsoft SQL Azure will be made.
Toad allows you to connect to SharePoint via OData service to view and query SharePoint lists as tables. Toad supports SharePoint 2010 and 2013. You can also create a connection to SharePoint Online.
After creating a connection, see About SharePoint Data Sources for more information.
To create a SharePoint connection
on the Connections toolbar (ALT+F+N).
Enter the connection information in the Create New Connection dialog. Review the following for additional information:
| URL |
Enter the full URL address to the SharePoint OData service endpoint for the SharePoint site to which you want to connect. The URL address should have the following format: http://<servername>/_vti_bin/listdata.svc |
| Authentication |
Select the type of authentication to use for this connection. Toad offers two options:
The required login fields will be enabled or disabled according to the authentication type that is chosen. |
| Username |
For SharePoint—Enter your Windows user name to use when connecting to this SharePoint site. For SharePoint Online—Enter the user name to use when connecting to this instance of SharePoint Online. |
| Password |
Enter the password to use when connecting. Tip: After connecting, you can set a master password to further secure your connection in Tools | Options| Environment | Security. |
| SharePoint Online | Select this option if creating a connection to a SharePoint Online instance. |
| Category | (Optional) Select an existing category or create a new one. |
|
Note: In NoSQL and Business Intelligence connections, Toad automatically saves the password in the connections.xml file as obfuscated text, as well as in Toad. To add additional password security, use Toad's Master Password feature. | |
Tips:
To create this type of connection to SharePoint, Active Directory Universal with MFA needs to be selected from the Authentication field dropdown.
The next step is to enter a user name which has been configured for multi-factor authentication and click on Connect.
Toad Authentication Window will appear allowing you to select either Windows Authentication or AzureADTrust for the type of credentials which will be used for the connection.
The step that follows will enable you to select a user from the list or add another one by clicking on Use another account.
After that, you will be prompted to enter your credentials and depending on the type of authentication that the account has been configured with, you will undergo an additional authentication step, such as the one in the image below.
After completing the final authentication step, a successful connection to SharePoint will be made.
Setting a default SharePoint connection in Tools|Options|Environment is currently available only for Basic Authentication
Review the following solutions to help troubleshoot SQL Server connection issues in Toad.
| Issue | Cause/Solution |
|---|---|
|
Cannot specify a port number when connecting |
Currently, Toad does not have a separate field for specifying a port number. Solution: You can connect if you know the port number for the instance by entering the following in the Server name field on the New Connection window: ServerName,Port or IPAddress,Port For example: 10.1.29.129,1234 (where 1234 is the port number of the instance) |
|
Cannot connect to a remote instance in SQL Server 2005 |
Remote connections may not be enabled in SQL Server 2005. Also, named instances are configured to use dynamic ports and select an available port once the SQL Server Service starts. If you are connecting to a named instance through a firewall, configure the Database Engine to listen on a specific port, so that the appropriate port is opened in the firewall. Note: Remote connections are disabled by default in the Express and Developer editions of SQL Server 2005. Solution: To enable remote connections, see "How to configure SQL Server 2005 to allow remote connections" at: http://support.microsoft.com/kb/914277 |
|
"Path is not of a legal form" error message when connecting or "Could not find a part of the path |
You attempted to migrate settings from a previous install of Toad to the current install, but the settings file (InitialSqlServer.Sql) for the previous install was either removed, moved, or corrupt. You may also receive this error if you installed Toad and migrated settings from a previous version, and later uninstalled the previous version. Solution: You must specify a valid location for the InitialSqlServer.Sql file in Toad. To specify a valid location
By default, this file is located in the following directory: C:\Program Files\Quest Software\Toad Data Studio version \Templates\Scripts Note: Clicking |
| Cannot establish Named Pipes connection |
If you are trying to connect to the server using Named Pipes, "Poll service status in connection list" option should be cleared. Solution:
|
| Cannot access some functionality when working with Azure connection. |
To utilize majority of Toad functionality VIEW DEFINITION grant is required for those databases you want to work with. |
to display any servers running SQL Server that are currently active on the network.