I tried to create a connection in SQL Developer with a remote SQL Server database. The first steps to configure Oracle SQL Developer are described in the introductory article to SQL Developer, and had already done some testing with a SQL Server installed on the same machine as SQL Developer, but when I tried to do it with a remote BD SQL Server I found some additional difficulty that I think it's interesting to comment.
The first thing to consider is that the port to connect with the database will be open in the remote server for the machine where we have our SQL Developer. To check if we access from our machine we can use a simple telnet indicating the ip or the domain of the remote server and the port used for SQL Server, normally 1433:
$ telnet 192.168.0.107 1433
If we do not have a message error we have free way. If the result is something like 'Unable to connect to remote host' something doesn't let us get to the server. It can be a lot of things, but usually it's just that the port is protected by the firewall server. To open the port on the server, just follow the steps on the help topic How to configure Windows Firewall to access the database engine MSDN Library. I extract now the most relevant part:
- For Windows XP and Windows Server 2003:
To open a port in Windows Firewall for TCP access:
From the Start menu, click Run, type firewall.cpl, and then click OK.
In the Windows Firewall dialog box, click the Exceptions tab and then click Add Port.
In the dialog box Add a port in the box Name, type SQL Server <instancename>.
In the box Port Number, type the port number of the Database Engine's instance, for example, 1433 for the default instance.
Check that TCP is selected and click OK.
To open the port and expose the SQL Server Browser service, click Add Port, type SQL Server Browser in the text box Name, type 1434 in the text box Port number, select UDP, and then click OK.
- For Windows Vista, Windows Server 2008 and later versions are the same steps, but instead of running the program run wf.msc firewall.cpl
Once the way is clear, it's only a matter of configure the connection by selecting the tab for SQL Server, but this is where I found more problems. In the Authentication Using the database I didn't had problems, the data from a user who has access to the database of interest is reported, and the connection works.
I find the problem when I check the 'Use Windows Authentication', I tried in many ways and I did not succeed, I can only connect to a database user, so I'll leave it open, here and in the forum if anyone knows exactly how to report parameters to connect from Oracle SQL Developer (v1.5) with a remote SQL Server database using Windows Authentication.