Microsoft SQL Server LocalDB

To connect to your LocalDB instance with DataGrip, check if your LocalDB instance is ready for a connection. To do that, locate SqllocalDB.exe and run the following command in a command prompt:

You will see a list of available LocalDB instances on the server.

Next, create a LocalDB instance. To create an instance, run the following command:

This command creates an instance of LocalDB named DEVELOPMENT by using SQL Server 2017 binaries and starts the instance. If you omit 15.0, the version number defaults to the version of the SqlLocalDB utility.

To check an instance state, run this command.

Currently, the instance is running (see the State field). If you have the Stopped state, start the instance by running the following command in the terminal.

Open data source properties. You can open data source properties by using one of the following options:

• Navigate to File | Data Sources.

• Press Ctrl+Alt+Shift+S.

• In the Database Explorer (View | Tool Windows | Database Explorer), click the Data Source Properties icon .

From the Driver list, select Microsoft SQL Server LocalDB.

At the bottom of the data source settings area, click the Download missing driver files link. As you click this link, DataGrip downloads drivers that are required to interact with a database. The IDE does not include bundled drivers in order to have a smaller size of the installation package and to keep driver versions up-to-date for each IDE version.

You can specify your drivers for the data source if you do not want to download the provided drivers. For more information about creating a database connection with your driver, see Add a user driver to an existing connection.

From the Instance list, select the instance to connect to (for example, DEVELOPMENT).

From the Authentication list, select the authentication type:

• User & Password: connect by using a username and a password.

• Windows credentials: connect by using your Windows domain creadentials. Requires to run DataGrip on Windows in the same domain as the Microsoft SQL Server database. Works as the Single-Sign On (SSO).

• Kerberos: connecting by using Kerberos authentication. Requires a Kerberos server and authentication with kinit.

• No auth: connect without authentication.

• Domain credentials: connect by using a domain, a username, and a password.

To ensure that the connection to the data source is successful, click the Test Connection link.