- First, I need to make sure that the SQL server is up and running.
- After that, I'll test the connection using Python or an UDL file.
- If that works, I'll connect using NodeJS
Step 1: SQL Server
From the app Sql Server Configuration Manager, SQL Server is running on my machine.
SQL Server Browser isn't active however. That app provides information about SQL resources and SQL server instances on this computer. It listens to UDP port 1434 and allows several different SQL Server instances on the same port.
If TCP/IP is enabled for a SQL server, that server is assigned to a port. In addition, it is possible to make the server listen to a specific pipe.
SQL Server reads out all active instances of the computer and notes their corresponding ports and pipes.
It is possible to reach SQL servers without the SQL Server Browser running on the host, but then the port (and pipe) needs to be specified. It may be necessary to open up a couple of ports in the firewall, such as 1433 and 1434.
First Attempt to Connect to SQL Server Using Python:
 |
| The script can't find the SQL server. |
Second Attempt to Connect to SQL Server Using Python:
 |
| Now, the script can find the SQL server but it can't find the data source. |
Now, the script seems to have come a bit further. It doesn't complain about not finding SQL Server anymore. Instead, it says that it can't find the data source. The reason is most likely because I've specified the wrong version of ODBC Driver.
Third Attempt to Connect to SQL Server Using Python:
This time I'll specify the actual version of SQL driver: 17.
 |
| Yay! |
Now, I know that the SQL Server is up and running on my local computer, and I know how to access it from Python. The next step is to connect using a NodeJS script. I'll explore that in the next blog post.
No comments:
Post a Comment