Kevin is a Software Developer with 20 years experience designing and building business intelligence and system integration solutions.
Importing Data from MSSQL Server
Over the years Microsoft has greatly improved how Excel integrates with other databases, including of course, Microsoft SQL Server. Each version has seen many improvements in ease of functionality to the point where extracted data from many sources is as easy as it gets.
In this example, we will extract data from a SQL Server (2016) but this will equally well with other versions. Follow these steps to extract data:
From the Data tab click on the Get Data drop-down menu as shown in figure-1 below and select the From Database section and finally From SQL Server Database which will the display of an input panel to enter the server, database and credentials.
The SQL Server database connection and query interface shown in figure-2 allows us to enter the name of the server and optionally the database where the data we need is stored. If you don’t specify the database, in the next step you will still need to select a database, so I highly recommend that you enter a database here to save yourself the extra steps. Either way, you will need to specify a database.
Or, write a query by click on the Advanced options to expand the custom query section which is shown in figure-3 below. Although the query field is basic, meaning that you should use SSMS or another query editor to prepare your query if it is modestly complex or if you need to test it before using it here, you can paste in any valid T-SQL query that returns a result set. This means that you can use this for INSERT, UPDATE or DELETE SQL operations.
- A couple of additional information regarding the three options under the query field. These are “Include relationship columns”, “Navigate full hierarchy” and “Enable SQL Server failover support”. Of the three I find the first one the most useful and is always enabled by default.
- The “Include relationship columns” option will tell SQL Server to automatically include any columns in another table that has a relationship with any of the columns in the tables that are included in the query.
- Navigate full hierarchy expands the tree view of the tables and columns that are included in the query
- iii. Enable SQL Server failover support ensures that, in case, the server connection fails or if there are too many connections on one server, you the connection will automatically switch to another connection/server in the cluster. This option is only useful if you have a SQL Server farm that is configured as a cluster with failover.
Export Data to Microsoft SQL Server
Basically, you need to connect to a database, assuming of course you have “write” (insert) permission on the database and the table, then
- Write an insert query that will upload each row in your dataset (it is easier to define an Excel Table – not a DataTable).
- Name the table in Excel
- Attach the VBA function to a button, or macro
Enable Developer Mode
Next, open the VBA editor from the Developer tab to add VBA code to select the dataset and upload to SQL Server.
Query = “INSERT INTO your_SQL_table_name” & _ “SELECT * from your_excel_table_name ”
Using this method, while easy, assumes that all the columns (count and names) match the number of columns in your database table and have the same names. Otherwise you will need to list the specific column names, like:
Query = “INSERT INTO your_SQL_table_name (column1, column2, column3, etc.)” & _
“SELECT column1, column2, column3 from your_excel_table_name”
If the table doesn’t exist, you can export the data and create the table using one simple query as the following:
Query = “SELECT * INTO your_new_table FROM excel_table_name”
Query = “SELECT col1, col2, col3 INTO your_new_table FROM excel_table_name”
The first way, you create a column for every column in the excel table. The second option allows you to select all the columns by name or a subset of the columns from the Excel table.
These techniques are the very basic way to import and export data to Excel. Creating tables can get more complicated if you can to add primary keys, indexes, constraints, triggers and so on but is another subject.
This design pattern can be used for other databases as well like MySQL or Oracle. You would just need to change the driver for the appropriate database.
This article is accurate and true to the best of the author’s knowledge. Content is for informational or entertainment purposes only and does not substitute for personal counsel or professional advice in business, financial, legal, or technical matters.
© 2019 Kevin Languedoc
Kevin Languedoc (author) from Canada on June 30, 2020:
check your variables, especially the objects. Make sure you declare them with DIM object as Class. The you must initialize them using SET. so SET object = new class or SET object = some value
Dayanand GS on June 30, 2020:
I am getting error of "object variable or with block variable not set"
How to fix it
Kevin Languedoc (author) from Canada on May 28, 2020:
Can you share error message. Also, did u define "command"
Kevin Languedoc (author) from Canada on May 28, 2020:
can you share error message
Carlos Cortinas on May 24, 2020:
Hi Kevin, I'm using your code in order to export data from Excel to SQL Server, but I don´t know why I get an error in the line of "command.CommandType = adCmdText"
Could you help please.
Kevin Languedoc (author) from Canada on March 15, 2020:
Can you share your code so I can have a better idea what you are doing. Also, did you define table in Excel?
Ketanscm on March 14, 2020:
I am trying to export data from excel to SQL server with your code.
However, I am getting error on command.execute line. Error shown is "invalid object name KKKMMM" where KKKMMM is table name in my active worksheet. pl help.