From the drop-down menu, select the data access mode as SQL Command

Data access mode: We will use the SQL query specified above section.

OLE DB connection Manager: Specify SQL Server instance details in the connection manager.

Rename the source and destination as per below:ĭouble-click on the JSON file data and in the OLE DB source editor, do the following tasks: In the data flow tab, drag the OLE DB Source and OLE DB destination as shown below:

In this package, drag Data Flow Task in the control flow task and rename it to Data import from the JSON file:ĭouble-click on this data import from the JSON file task and it moves the package in the data flow tab. Open Visual Studio 2019 and create a new integration service project in a suitable directory. I am using Visual Studio 2019 with SSDT package in this article. If you are not much aware of it, I would recommend reading SQLShack articles. You should have basic knowledge of SSIS packages. We can use SQL Server integration package for inserting JSON into the SQL Server table as well. SSIS package for importing JSON data into SQL Server table The following query, imports data from results.json, creates a JSON table automatically using SQL SELECT INTO statement and inserts data into it: We can also create a table using the SQL SELECT INTO statement similar to a relational DB table. We can use the similar t-SQL described earlier for inserting data in an existing table. Import JSON file data into the SQL Server table It seems SQL Server uses a fixed estimate of 50 rows for JSON data import: In this execution plan also, it estimates the number of rows 50 in comparison with the actual 290 rows. Let’s import another JSON file having 290 records and view the actual execution plan. We see a difference between the estimated number of rows (50) and an actual number of rows (10) as query optimizer unable to estimates the correct number of rows for JSON input

It uses object for fetching the columns and their values In the above execution plan, note the following: Let’s hover the cursor over it and view the details: In this plan, we can note that it uses a table-valued function for OPENJSON. In SSMS, click on Actual Execution Plan and execute the previous SQL statement. View actual execution plan for JSON data import In this output, we do not see the EmailPromotion column even if it is available in the JSON:

Open json in excel