To import a worksheet into SQL Server, connect to the Database Engine in SQL Server Management Studio (SSMS), right-click the destination database, and choose Tasks > Import Data. Set Excel as the source and SQL Server as the destination, select a worksheet or range, inspect the column mappings and preview, then run the transfer. Check provider compatibility and inferred data types before you commit the import.
Before you start
- Keep the workbook on a path accessible to the computer running the wizard. It can be a local path or a network share. The wizard cannot open a password-protected Excel workbook. See Microsoft’s Excel data source connection guidance.
- Know the SQL Server instance and destination database, and have the connection details and access you need. The wizard asks for the server, authentication method, and database.
- If Excel is missing from the source list, check provider and wizard compatibility before changing workbook settings. The version-specific details are in the troubleshooting section below.
Open the Import and Export Wizard
- In SSMS, connect to an instance of the SQL Server Database Engine.
- In Object Explorer, expand Databases, right-click the destination database, and select Tasks > Import Data. Microsoft’s wizard launch instructions give this path.
Set Excel as the source
- On the Choose a Data Source page, choose Microsoft Excel and browse to the workbook.
- Select the Excel version that matches the workbook and the installed connectivity components. The version shown in the dropdown does not necessarily mean its provider is installed.
- Set First row has column names to match the sheet. When enabled, the first row is used as headings rather than imported as data. When disabled, an existing header row is treated as data; when there are no headers, the wizard assigns names such as F1 and F2.
The source list can include worksheets, usually shown with a $ suffix, and named ranges. You can also specify a cell range. For a walkthrough of the Excel source settings, see Microsoft’s Import and Export Wizard example and its Excel connection reference.
As an Amazon Associate I earn from qualifying purchases.
Set SQL Server as the destination and choose what to copy
- On the Choose a Destination page, select the SQL Server destination provider and enter the server, authentication, and database details.
- On Specify Table Copy or Query, choose the option to copy tables or views for a straightforward worksheet import. Choose query mode when you need to select particular source data or use a range.
- On the source and destination selection page, select the worksheet or range and specify whether to create a new table or load an existing one. Review any generated table name and change it if needed.
Microsoft’s wizard example illustrates the source, destination, and table-mapping flow.
Review mappings and preview before running
Use Edit Mappings to check destination column names and data types. Use Preview to confirm that the intended worksheet or range, headers, and sample rows appear correctly. Then proceed through the execution pages and review the completion result. Microsoft documents both mapping and preview in its wizard walkthrough.
#1 Best Overall
Pay particular attention to text columns. Microsoft warns that Excel driver sampling can infer a 255-character string column if the sampled rows do not contain longer values; longer text may then be truncated. This is a possible inference problem, not a claim that every import truncates text. Inspect long values and their destination mappings before executing. See Microsoft’s Excel and SSIS guidance.
Troubleshoot common problems
Microsoft Excel is not listed as a source
The wizard and Excel provider need compatible architectures. Microsoft notes that Excel providers are often 32-bit and may not appear in a 64-bit wizard. However, do not apply that general guidance blindly to newer versions: Microsoft says the wizard in SSMS 21 and SQL Server 2025 supports only 64-bit, and directs users in that environment to ACE OLEDB 16.0 for Excel connectivity. Check the guidance for your installed versions before installing or changing components. See Microsoft’s wizard overview and Excel provider guidance.
The selected Excel version gives a provider error
A version appearing in the source dropdown does not establish that a compatible provider is installed. Confirm the installed connectivity components and their architecture against the wizard you are running. Microsoft explains the version and provider considerations in its Excel data source connection reference.
Free tools Windows power users keep installed
One-click scans. No signup required.
Column names are wrong or the first record is missing
Recheck First row has column names and inspect the preview. The setting determines whether the first row supplies headings or is loaded as a record; with no headers, the wizard uses generated names such as F1 and F2.
Rank #3
The workbook is password-protected
The wizard cannot open password-protected Excel workbooks. If your organization permits it, prepare an authorized unprotected copy for import, following its data-handling rules.
You need several worksheets or a repeatable import
Microsoft says these tools typically need to be run once per worksheet. For a recurring or customized workflow, the wizard settings can be saved as an SSIS package and maintained as a package. See Microsoft’s Excel import overview.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When the destination is Azure SQL Database
Microsoft’s overview says direct import from Excel to Azure SQL Database is not available through this workflow. Save the worksheet as CSV, then use a supported text or flat-file import route for the Azure destination. This limitation is specific to the Azure SQL Database path described there; it should not be generalized to on-premises SQL Server. See Microsoft’s Excel import overview.
Choose a workflow for the job
| Need | Suitable approach | What to consider |
|---|---|---|
| One-time import to on-premises SQL Server | SSMS Import and Export Wizard | Guided process; verify provider compatibility, mappings, and inferred types. |
| Repeatable or customized package | SSIS package using an Excel Source and SQL Server destination | Requires package setup and ongoing maintenance; wizard settings can be saved and customized as SSIS. |
| Azure SQL Database destination | Save the worksheet as CSV, then use a supported flat-file import route | Adds an export step; Microsoft says direct Excel import is unavailable for this destination. |
| Only selected rows or a range | Wizard query mode or an Excel range | Requires a valid query or range and compatible provider support. |
These workflow distinctions are described in Microsoft’s Excel import overview and wizard example.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
