 |
|
Insert, Update or Delete Data in SQL Server from Excel
|
By: Jeremy Kadlec | Read Comments (8) | Related Tips: 1 | 2 | 3 | 4 | 5 | More > Microsoft Excel Integration |
Problem
I have seen your previous tips (Export data from SQL Server to Excel and Different Options for Importing Data into SQL Server) related to working with Excel and SQL Server data. The main command used in one of the tips is OPENROWSET. This has been beneficial for us because in our environment because our business users provide data to us in the form of Excel spreadsheets. Many of the situations end up translating to INSERT, UPDATE or DELETE code in one or more of our SQL Server databases. We always upload the data to a table and then begin the process. Although this process works are you familiar with any other options to directly perform the INSERT, UPDATE or DELETE operations? Are their any benefits to transitioning our code to another approach with the OPENROWSET command?
Solution
Yes - You are correct the OPENROWSET command can directly support INSERT, UPDATE or DELETE operations as shown in these tips: Export data from SQL Server to Excel and Different Options for Importing Data into SQL Server. In addition, the OPENROWSET command can also support SELECT statements where a table is joined to the Excel spreadsheet. Let's work through some examples with the SQL Server 2005 AdventureWorks sample database for each operation with a sample Excel spreadsheet.
Prerequisites
For all of these examples, please do the following:
- Download this Excel (Office 2003) spreadsheet to perform the operations.
- In order to follow the examples, be sure to save the Excel spreadsheet into a directory called C:\MSSQLTips\.
- Review each of the worksheets in the Excel file to see the different data.
- Be sure to close the Excel spreadsheet before running any of the code.
- Review each of the commands below before executing them in your environment.
OPENROWSET Examples
Below are four examples to show some of the flexibility with the OPENROWSET command:
|
SELECT with a JOIN and ORDER BY Clause |
| Code Explanation - With the query below, 5 records should be returned to show a simple INNER JOIN statement can return a single result set from both data in the table ([Sales].[SalesPerson]) and Excel spreadsheet. |
| SELECT SP.[SalesPersonID] ,SP.[TerritoryID] ,SP.[SalesQuota] ,SP.[Bonus] ,SP.[CommissionPct] ,SP.[SalesYTD] ,SP.[SalesLastYear] ,SP.[rowguid] ,SP.[ModifiedDate] ,T.[SalesPersonID] ,T.[TerritoryID] FROM [AdventureWorks].[Sales].[SalesPerson] SP INNER JOIN OPENROWSET('Microsoft.Jet.OLEDB.4.0', 'Excel 8.0;Database=C:\MSSQLTips\1540_OPENROWSET_Examples.xls;', 'SELECT SalesPersonID, TerritoryID FROM [SELECT_Example$]') T ON SP.[SalesPersonID] = T.[SalesPersonID] AND SP.[TerritoryID] = T.[TerritoryID] ORDER BY SP.[SalesPersonID], SP.[TerritoryID] GO |
|
INSERT with a SELECT Statement |
| Code Explanation - With the first block of code, five records are inserted into the [AdventureWorks].[Sales].[SalesPerson] table by reading the data from the INSERT_Example worksheet of the Excel spreadsheet. In the second query, the data inserted is verified. |
| INSERT INTO [AdventureWorks].[Sales].[SalesPerson](SalesPersonID, TerritoryID, SalesQuota, Bonus, CommissionPct, SalesYTD, SalesLastYear, rowguid, ModifiedDate) SELECT SalesPersonID ,TerritoryID ,SalesQuota ,Bonus ,CommissionPct ,SalesYTD ,SalesLastYear ,NEWID() ,GETDATE() FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0', 'Excel 8.0;Database=C:\MSSQLTips\1540_OPENROWSET_Examples.xls;', 'SELECT SalesPersonID, TerritoryID, SalesQuota, Bonus, CommissionPct, SalesYTD, SalesLastYear FROM [INSERT_Example$]') GO SELECT * FROM [AdventureWorks].[Sales].[SalesPerson] |
|
UPDATE with a JOIN Statement |
| Code Explanation - With the first block of code, five records are updated in the [AdventureWorks].[Sales].[SalesPerson] table by reading the data from the UPDATE_Example worksheet of the Excel spreadsheet. In the second query, the data updated is verified. |
| UPDATE SP SET SP.Bonus = T.Bonus FROM [AdventureWorks].[Sales].[SalesPerson] SP INNER JOIN OPENROWSET('Microsoft.Jet.OLEDB.4.0', 'Excel 8.0;Database=C:\MSSQLTips\1540_OPENROWSET_Examples.xls;', 'SELECT SalesPersonID, TerritoryID, SalesQuota, Bonus FROM [UPDATE_Example$]') T ON SP.SalesPersonID = T.SalesPersonID AND SP.TerritoryID = T.TerritoryID AND SP.SalesQuota = T.SalesQuota GO SELECT * FROM [AdventureWorks].[Sales].[SalesPerson] |
|
DELETE with a JOIN Statement |
| Code Explanation - With the first block of code, five records are deleted in the [AdventureWorks].[Sales].[SalesPerson] table by reading the data from the DELETE_Example worksheet of the Excel spreadsheet. In the second query, the data deleted is verified. |
| DELETE SP FROM [AdventureWorks].[Sales].[SalesPerson] SP INNER JOIN OPENROWSET('Microsoft.Jet.OLEDB.4.0', 'Excel 8.0;Database=C:\MSSQLTips\1540_OPENROWSET_Examples.xls;', 'SELECT SalesPersonID, TerritoryID, SalesQuota, Bonus FROM [UPDATE_Example$]') T ON SP.SalesPersonID = T.SalesPersonID AND SP.TerritoryID = T.TerritoryID GO SELECT * FROM [AdventureWorks].[Sales].[SalesPerson] |
General Analysis
In terms of transitioning your code to the new approach, I have yet to experience any performance issues with 1000's of records, but that seems to be the first concern. If you test the approach and the overall performance is not an issue, then consider the approach. It also may be faster to perform a single UPDATE as is the case with the example above versus uploading (INSERT...SELECT) the data and then performing an UPDATE based on the new table. In addition, by using the commands listed above versus a two step process the overall code may be a little bit cleaner. A second consideration with SQL Server 2005 is that the Surface Area Configuration setting must be enabled to use this code in either case. Finally, with either approach be sure to clean up any Excel spreadsheets or temporary tables once you are finished with them.
Next Steps
- If you are faced with a need to upload Excel based data to SQL Server consider the code samples in this tip as an option to do so.
- As alternatives to these commands, you can also check out these tips:
- Export data from SQL Server to Excel
- Different Options for Importing Data into SQL Server
- Importing Excel data with SQL Server Integration Services (SSIS) and dealing with unicode and non-unicode data issues
- MSSQLTips.com Category: SQL Server Integration Services
- MSSQLTips.com Category: Data Transformation Services
- MSSQLTips.com Category: Microsoft Office Integration
- One item to keep in mind with any process is to make sure all of the supporting files, tables, etc are organized and/or removed once they are no longer needed.
Last Update: 7/15/2008
About the author
View all my tips
PrintComments and Feedback:
| Tuesday, July 29, 2008 - 6:29:49 PM - ddnikon | Read The Tip |
|
I coded the example exactly as described, enabled the xp_cmdshell, and downloaded the Excel spreadsheet. However, the SalesPersonId's were different than the Id's in the table, the table ID numbers started in the 200's ( 268, 275, 276, etc.), so I hanged them on the spreadsheet. The query runs successfully, but no rows are updated, and cannot figure out why. Do you have any suggestions? Here's the code I'm using..... Thanks for any help you can give. Don UPDATE SPSET SP.Bonus = T.BonusFROM [AdventureWorks].[Sales].[SalesPerson] SPINNER JOIN OPENROWSET('Microsoft.Jet.OLEDB.4.0','Excel 8.0;Database=C:\MSSQLTips\DD_OPENROWSET_Examples.xls;' ,'SELECT SalesPersonID, TerritoryID, SalesQuota, Bonus FROM [UPDATE_Example$]' ) TON SP.SalesPersonID = T.SalesPersonIDAND SP.TerritoryID = T.TerritoryIDAND SP.SalesQuota = T.SalesQuotaGO |
|
| Monday, August 11, 2008 - 8:02:08 AM - odeddror | Read The Tip |
|
Hi there, Idon't know if this is the right place but I'm using Windows Vista Business x64 SP1 and SQL Server 2005 Devloper x64 SP2 When I ran this example I'm getting (even I set in SQL configuration OPENROWSET ON) Msg 7403, Level 16, State 1, Line 1 The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered. Maybe do you have tip on this issue?
Thanks, Oded Dror |
|
| Monday, August 11, 2008 - 8:22:29 AM - ddnikon | Read The Tip |
|
Do you have a sample of the code you're using? Might be a stupid question, but have you created the spreadsheet and used the same name in the code? |
|
| Saturday, August 16, 2008 - 8:53:36 PM - odeddror | Read The Tip |
|
Yes I did |
|
| Tuesday, July 03, 2012 - 12:25:17 PM - richard | Read The Tip |
|
Hi, You might like to know about a different approach - you can try this for free – and includes templates and validation as well as sending data from excel to stored procedures as well as tables. Thank you for your interest
|
|
| Sunday, November 18, 2012 - 12:13:57 PM - ary | Read The Tip |
|
I followed the steps above however i get the following error:
Msg 7399, Level 16, State 1, Line 1
Please help. I used sp_configure to enable ad hoc remote queries and OLE automation in SQL Facets. Also suggest if there is a way to update excel data using vba macros or otherwise without having to log in to ssms? |
|
| Monday, November 19, 2012 - 9:40:13 AM - Jeremy Kadlec | Read The Tip |
|
Ary, Can you post the code that is causing the issue? What SQL Server version, service pack and edition of SQL Server are you working on? Thank you, |
|
| Monday, November 19, 2012 - 8:21:11 PM - Ary | Read The Tip |
|
Hey Jeremy, Thank you so much for considering to help. I figured I could accomplish that using ADODB. I would love to learn how to use OLEDB too. Following are my SQL System details: I'm using MS Office 2010 Excel VBA.
|
|
|
privacy | disclaimer | copyright | advertise | about authors | contribute | feedback | giveaways | user groups Some names and products listed are the registered trademarks of their respective owners. Edgewood Solutions LLC | MSSharePointTips.com | MSSQLTips.com |