While configuring your Microsoft SQL Server connection, you may encounter several issues. Understanding these common errors can help streamline the setup process and facilitate quick resolutions.
Wrong input data
Error messages:
{%docs-informer error%}
"Failed to connect to the server. Please check that host and port are correct. If your database is behind a firewall, make sure you whitelisted our IP's and select "Use static IP = YES" in connection parameters."
"Login failed for user 'your_username'. Please check that the username, password, and database name are correct."
"The specified schema name "your_schema_name" either does not exist or you do not have permission to use it."
{%docs-informer-end%}
General solution
Server Connection:
- Verify the host address and port number for the SQL Server.
- If behind a firewall, whitelist the required IP addresses and enable "Use static IP = YES" in the connection settings.
Login Credentials:
- Confirm the accuracy of the username, password, and database name. Reset credentials if necessary.
Schema Access:
- Check if the specified schema name exists and that the user account has the required permissions to access it. Grant permissions if needed.
Refer to the Documentation if necessary.
Wrong permissions
Error message:
{%docs-informer error%}
"Permission denied. You should grant all permissions specified in the docs."
{%docs-informer-end%}
Solution
Grant Required Permissions:
- Ensure that all necessary permissions are granted in Microsoft SQL Server as detailed in the documentation. This includes permissions for operations like ```BULK INSERT```, ```INSERT```, ```CREATE```, ```UPDATE```, ```DELETE```, and ```SELECT```.
Configure Schema Access:
- Verify and adjust access permissions to specific schemas, including the dbo schema, ensuring the user account can perform the required operations.
Update Server Settings:
- Adjust server settings to reflect these permission changes, aligning with the documentation guidelines.
Test Permissions:
- After making changes, test the server access to confirm that the permission-related issues are resolved.
{%docs-informer info%}
If none of the provided solutions worked, feel free to raise a request via the
Service Desk
{%docs-informer-end%}