Datagrip connecting SQL Server connecting Datagrip to MS

Connecting Datagrip to MS SQL Server

Posted on June, Maksim Sobolevskiy

Some specific needs of SQL developers like connecting to SQL Server from OSX and even using Windows authentication can is Covered by Datagrip. Since releasing Datagrip, we ' ve received lots of comments about connecting to SQL Server. It appears it ' s not straightforward as with other databases, requiring a couple of extra steps beforehand. Here are a small guide describing the main problems your may face and how to solve them.

First, ensure that important options in SQL Server Configuration Manager is configured correctly. Make sure the SQL Server Browser is running:

TCP/IP connections need to BES enabled:

To know the port for the connection just click on TCP/IP. In our case, it's default port 1433.

If you end up changing anything, restart the server. For most situations, this would resolve connection problems, your server would accept remote connections and you is ready t O go. If you still has problems, it could be this TCP port needs to being adjusted or the remote connection to SQL server needs to be enabled with its settings. This tutorial would walk you through it, but we'll also describe the process here.

Invoke Database View by pressing alt/cmd+1 and create a new data source with the appropriate driver. If you use a Microsoft driver, note that it supports SQL Server and later versions. Here we'll assume it ' s the Jtds driver.

If you have no driver, download it by clicking the link.

Then enter the host name, the instance name and the credentials. Remember that Datagrip offers completion for host, instance and database names (ctrl/cmd+space), but the name of The database is optional. For those who is used to the SSMS interface, let's compare the connection windows.

If the port number conflicts with the instance name, in the Jtds driver, the instance name would take precedence over the P ORT number, while the opposite would happen in the Microsoft driver. To avoid confusion, simply remove the port number. If you strongly wish to specify the port number, click the auto-set button (located to the right of the Instance field) to has the port number set automatically. But remember, the port number can be changed the restart the server.

If you need the use of Windows authentication, only Microsoft driver would let you do it.

The other-the-connect to-the server with Windows authentication are to use domain authentication of JTDS driver, which l ETS connect from any other machine. What's notable, it works on any OS. To does this, go to the Advanced tab of data source properties, set USENTLMV2 to true and specify the DOMA In name in the DOMAIN field.

Then enter your Windows credentials in the user/password fields and click Test Connection.

If you want to check which particular databases or schemas is shown in the database view, go to the Schemas tab In Data Source properties:

Already using Datagrip 2016.2 EAP, use more Schemas ... in the database view:

All selected databases'll appear in the database view. This is what it looks in SQL Server Management Studio:

And here's how it looks in Datagrip:

That ' s it! If you is experiencing any other problems, please tweet @ us or create a issue in our youtrack.

Your Datagrip Team

The drive to Develop

Datagrip connecting SQL Server connecting Datagrip to MS