Sql-server – Creating external tables from SQL Server using JDBC Drivers

It is unlikely that a named instance is running on port 1433, unless you explicitly set it as such. I also suspect that SSMS is using shared memory (if local) or named pipes (if remote), unlike JDBC which is using TCP/IP (and I don't know how to set JDBC to use a different protocol).

From this documentation, it seems your connection string should be:

jdbc:sqlserver://MS8AT09;instanceName=AT09;...

With no port designation. You could also try using the IP address instead of the name, in case name resolution is hampered for some reason.

Please check what port the instance is running on (look at SQL Server Configuration Manager)...

...and confirm your connection string does not hard-code a port that is different (JDBC might ). Do not hard-code the dynamic port, because it may not be the port used next time SQL Server starts. From Microsoft's documentation:

We recommend that the port number always be specified, as this is more secure than using sqlbrowser.

So, you may want to set your named instance to run on a specific port number, instead of using a dynamic port (the default), and then hard-coding that port number in the JDBC connection string. You can use the one that the instance was using dynamically, since you know it isn't in use by anything else. Also see KB #823938. So your connection string would become (assuming you used port 56737):

jdbc:sqlserver://192.168.0.65;instanceName=AT09;port=56737;...

I have found my answer from dbeaver support forum.

http://dbeaver.jkiss.org/forum/viewtopic.php?f=3&t=624&p=4261#p4261

First enable TCP/IP for your SQL instance in the SQL Server Configuration Manager tool.

1. Open SSCM and navigate to SQL Server Network Configuration > Protocols for SQLEXPRESS > TCP/IP

2. Enable the TCP/IP protocol in the Properties dialog for TCP/IP. (You can also enable it on the right-click menu.)

3. Set the TCP/IP port -- which can only be done in the Properties dialog (i.e., can't do it with just a right-click). On the "IP Addresses" tab of that Properties dialog, I used the IPAll settings at the bottom. Clear out TCP Dynamic Ports, then set TCP Port to 1433.

From within DBeaver, you can create either a jDTS or a "Microsoft Driver" connection

To create a jTDS connection in DBeaver

1. Create a new connection, specifying MS SQL Server | jTDS driver
2. Fill out the info on the first (General) tab, complete with User name and Password. I was able to enter my User name as just my Windows user name, not domain\username. But domain\username worked too, and that may be required on some networks. (I'm not sure.)
3. Go to the "Driver properties" tab and re-specify the DOMAIN and the USER as two separate parameters. I did not need to re-specify my PASSWORD on the "Driver properties" tab. And just to emphasize where to enter this: it's entered on the "Driver properties" tab -- not in the dialog box you get to by clicking the "Edit Driver Settings" button that's on the General tab.
4. Click the "Test Connection..." button to make sure it works, click Next a couple of times, then click Finish.

To create a "Microsoft Driver" connection in DBeaver

1. Create a new connection, specifying MS SQL Server | Microsoft Driver
2. Fill out the info on the first (General) tab, without specifying User name and Password (leave them blank).
3. Go to the Driver properties tab and set integratedSecurity=true. And, once again, just to emphasize where to enter this: it's entered on the "Driver properties" tab -- not in the dialog box you get to by clicking the "Edit Driver Settings" button that's on the General tab.
4. Click the "Test Connection..." button to make sure it works, click Next a couple of times, then click Finish.