Tutorial

Basics The source code of the object is the core part of the DDL script which is needed to create this object. In other words, the CREATE statement is not part of the object's source code. The source code is stored inside the database. The most common objects found with the source code are views, functions, and stored procedures.In many other tools, to update the source code, you would need to generate the CREATE OR REPLACE script, make the required changes and run it. In DataGrip it works a little differently. You just need to make the changes you need to make and the proper script will be

The 2021.1 update brings full native support for BigQuery. To learn how to use this, head over to our Documentation. This article covers support pre-2021.1 for BigQuery. If you are still using such a version, we encourage you to upgrade to the latest IDE version and check out the native support. Continuing the series of posts on how to connect DataGrip (or any other IntelliJ-based IDE) to various data sources, in this post we’ll show you how to connect to Google’s BigQuery. BigQuery is a low-cost enterprise data warehouse designed to handle data analytics at a massive scale. Currently, DataG

In the software world, there has been a solid habit of using version control to keep track and manage source code changes and collaboration. We have moved from centralized solutions like SourceSafe and TFS and now into using tools that distribute the management with Mercurial and Git. While both centralized and distributed technologies have pros and cons, we will be looking at why database professionals need to use version control and how to do it with the popular tool Git. With DataGrip’s inheritance from IntelliJ IDEA, we have the ability to use Git to store, manage edits, and allow a tea

If you use the AWS cloud, then you probably store data on their S3 platform, either for your application data or in the form of logs from services like the AWS Elastic Load Balancing. Amazon offers Athena, a service built on Presto, and allows you to query this S3 data using ANSI SQL syntax. So how to access this data straight from the IDE? To do this, we’ll first need to do some configuration to connect the IDE with Athena. Head towards the Database Tool Window, then select Data Source Properties, click on the “+” button and then, at the bottom of the list you’ll see an entry named Driver,

Hello, In this tutorial we’re going to look at three popular use-cases: — Duplicate a data source within one project. — Share data sources between projects inside one IDE. — Copy a data source from one IDE to another IDE, or to another computer. Duplicate a data source within one project A trivial problem deserves a trivial solution: in the context menu of the selected data source, click Duplicate or press Ctrl/Cmd+D. A new data source will be created with the same properties, including the password. Share data sources between projects inside one IDE In IntelliJ-based IDEs, a data source

DataGrip lets you run scripts against the selected schema objects. For example, you can generate Java classes from tables or, if you want, classes in any other language: C#, Python, etc. You can alter or extend the default functionality, for instance, generate an HTML or Markdown report. Out of the box, DataGrip can generate Java classes. To do this, go to the context menu of a table (or several tables) and press Scripted Extension → Generate POJO.groovy. Choose a destination folder, and that’s it! The class-file is ready. Generate POJO.groovy is just a script written in Groovy. It mean

In DataGrip, as well as all other JetBrains IDEs that feature database support, there is a powerful engine to export data in many formats. You can even create your own export format. Let’s look closer at this engine. Export directions Any table/view or result-set can be exported to a file or copied to the clipboard. To export to file:       — Context menu on a table/view and → Dump data to file.       — Context menu on a query and → Execute to file.       — In the toolbar of the result-set or data editor, selec

Search and navigation tips When you work with a software tool, you often need to find something or other. In DataGrip, you could be looking for things like: — Database objects: tables, views, procedures, columns and so on. — Data: enough said. — Code: for example a piece of code in a big script or the source code for a database object. — Lots of other things: files, settings, IDE actions, etc. Finding what you need easily is crucial to user experience, which is why we focus heavily on making search and navigation intuitive in DataGrip. Let’s look closer at how not to get lost in the IDE and

UPDATED: September, 2019 Check the LocalDB instance You can easily connect to your LocalDB instance with DataGrip. And as a first step, check if your LocalDB instance is ready for a connection. Locate SqllocalDB.exe and run the SqllocalDB.exe i command in a terminal. You will see a list of available LocalDB instances on the server. To create an instance, run SqlLocalDB create "DEVELOPMENT" 14.0 -s. This command creates an instance of LocalDB named DEVELOPMENT by using SQL Server 2017 binaries and starts the instance. If you omit 14.0, the version num

Some specific needs of SQL developers like connecting to SQL Server from OSX and even using Windows authentication can be 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 is a small guide describing the main problems you may face and how to solve them. Configure the SQL Server Configuration Manager To open SQL Server Configuration Manager, open the Search dialog on Windows and type SQLServerManager14.msc&nb