Skip to main content
7. Debug a SQL Server connection error

Debugging an error introduced in the SQL server connection configuration.

Praise Magidi avatar
Written by Praise Magidi
Updated over 7 months ago

Synatic has many connectors you can use to connect to a variety of data sources, Each data source environment is different and will require its own specific connection configuration and test.

In this article, we will use the SQL Server connection dialog and introduce a deliberate connection error and illustrate the Synatic response and how we resolve it.

There are two ways to test the connection, one way is to test immediately in the Edit Connection dialog and the other is when testing the flow. We'll illustrate the immediate Connection test first and then we'll run the flow test.


Testing the Connection

The Connection configuration dialog is shown below with the deliberate error.

While configuring the connection, it's always advisable to test the connection at this time by clicking on the Test button.

A connection error is displayed as the connection has failed to connect to the defined URL. You'll notice that the StatusCode shown is 500, meaning that an 'internal server error' has occurred.

πŸ“ All you need to do here is check that the URL you entered is complete and correct.


Testing the Flow

The other method is to test the flow that contains the error connection.

  • Click the blue play β–Ά button adjacent to the Pass Through step.

    πŸ“ This option lets you test the SQL Server connection step on the flow.

  • Because we inserted a deliberate error in the URL, you'll see the following error displayed 'Error connecting to the SQL Server'.

  • You'll notice that the StatusCode shown is also 500, meaning that an 'internal server error' has occurred.

    πŸ“ Again, all you need to do here is check that the URL you entered is complete and correct.


Correcting the error

Once you have corrected the error in the Edit Connection dialog, re-run the test again which should now execute successfully.

Did this answer your question?