To export DBeaver data to Excel, open a table or run a query, right-click its results grid, choose Export Data, select the XLSX format, set the destination, and complete the wizard. The resulting .xlsx file can be opened in Microsoft Excel; exporting a query result is usually the simplest way to control exactly which rows and columns go into it.
What DBeaver’s Excel export does
DBeaver’s data-transfer wizard can write database data to an Excel workbook in the XLSX format. You can start with a table or view, or with rows returned by a SQL query. The export creates a separate file; it does not turn the live database connection into an Excel connection, and changes made later in Excel do not update the database.
An export generally contains the data in the selected result set, arranged in columns and rows. It is useful for sharing a snapshot, reviewing results, making a report, or doing additional analysis in Excel. It is not the same as exporting a complete database backup: an XLSX file is not intended to preserve database indexes, constraints, stored procedures, permissions, or other database objects.
The precise wording and order of wizard pages can vary by DBeaver version and configuration. Look for the XLSX or Excel 2007–365 format in the format list. If it is available, the wizard will guide you through format, destination, and transfer options.
Export a query result to an XLSX file
A query is the most direct option when you need only a filtered subset, calculated columns, or a particular column order. For example, you could query orders for one month and select only the order date, customer ID, and total rather than exporting every column from a large table.
- Connect to the database and open a SQL editor for the connection.
- Write and run the query. Check the results grid for the expected columns, row count, filters, and sort order before exporting.
- Right-click inside the results grid and choose Export Data. In some layouts, a data-export control is also available from the results area.
- In the data-transfer wizard, choose the XLSX or Excel format, then continue to the output and format options.
- Choose a destination and filename ending in .xlsx. Review the remaining settings, then start the transfer.
- Open the finished workbook in Excel and inspect a few rows, especially dates, identifiers, nulls, and any values with many digits.
For a repeatable export, keep the SQL query or save it in DBeaver. That makes the data definition clear: someone can see which conditions and fields produced the workbook, instead of relying on an undocumented filter applied to a large table.
Export a table or view
To export a whole table or view, locate it in DBeaver’s Database Navigator, right-click the object, and choose Export Data. Select the XLSX format in the wizard and specify the output location. This is convenient for a quick copy of a small object, but it can transfer more data than you intended if the table is large.
If you need only some records, use a query with a WHERE condition rather than assuming the table export will infer your desired subset. For example, add a condition for a date range or status, and name only the columns needed. The database performs that filtering before DBeaver transfers the results, which can reduce both export time and the chance of sharing unrelated data.
Before starting, confirm which connection and object are selected. DBeaver may have several connections open at once, and similarly named tables can exist in different schemas or databases. Check the connection, schema, table name, and result columns rather than relying on the filename alone.
Choose the rows, columns, and output settings
The results grid is a useful checkpoint because it shows what the query returned. If the workbook should contain a particular order of columns, specify that order in the SELECT list. If it should contain only a defined group of rows, make the condition explicit in SQL. A database grid’s visible sorting or filtering behavior may not be identical across workflows, so verify the exported result rather than assuming a visual change was included.
Review the wizard’s format-specific options. Depending on the version and selected format, settings may include whether to write column names, how to handle null values, or how to organize output. If multiple result sets or objects are being transferred, check how the wizard is configured to produce the output before running it; do not assume they will all land in one worksheet in the layout you expect.
Excel allows at most 1,048,576 rows and 16,384 columns on a worksheet. A result that exceeds a worksheet limit cannot fit on one sheet. If a query may approach that size, reduce it with filters or export manageable segments, and check how the chosen DBeaver version handles oversized results. Do not assume it will automatically split a large result into neatly named worksheets.
Understand data types and Excel conversions
An XLSX file can represent values as dates, numbers, text, and other cell types, but the way a value appears in Excel may differ from how it appears in the database grid. Dates can be displayed using Excel’s regional date format, and timestamps may appear without the same precision or time-zone context shown by the database. Check important date and time fields after opening the file.
Long identifiers deserve special attention. Excel retains only 15 significant digits of numeric precision. A 16-digit account number or transaction identifier exported as a number can lose precision, even though it is an identifier rather than a quantity. If exact digits matter, return it as text in the query or use an export option that preserves it as text, then verify the cell values in Excel.
Leading zeros can also disappear if a code such as 00127 is interpreted as a number. Phone numbers, postal codes, product codes, and fixed-width identifiers are commonly better treated as text. Null database values may appear as blank cells, depending on the export settings; a blank cell is not necessarily equivalent to a database value of zero or an empty text string. Check these distinctions before using the workbook for calculations or reporting.
Handle large exports and performance carefully
Export duration depends on the database query, network, result size, and the way data is fetched and written. A slow export is not automatically a sign that DBeaver is stuck. For a very large table, first test the query with a limited or filtered result, confirm that it returns the right records, and then export the intended full set.
For large transfers, consider selecting fewer columns, applying a useful date or key range, or exporting separate logical batches. These changes can reduce the amount of data sent to DBeaver and avoid producing an unwieldy workbook. If the result is much larger than Excel’s worksheet limit, a text-based format or a database-native data workflow may be more suitable than XLSX.
Avoid changing fetch or connection settings without understanding their effect. They can influence how data is retrieved, but they do not remove Excel’s row limit or guarantee a faster transfer. If the database is shared, be mindful that a broad query can create load for other users. A targeted query is usually better than exporting everything and deleting unwanted rows afterward.
Common export problems and practical fixes
- XLSX is not listed: Check the available formats in the wizard and confirm that DBeaver is up to date. Format availability and labels can differ by version. If XLSX is unavailable, CSV is a practical fallback for plain tabular values.
- The file will not open or appears incomplete: Confirm the wizard finished successfully, the file has a .xlsx extension, and the destination has enough free space. Close the workbook if it is already open and locked by another application, then export to a new filename.
- Some rows or columns are missing: Recheck the SQL, filters, selected object, and result grid. Also check whether the output exceeds Excel’s worksheet limits or whether a transfer option restricted the exported data.
- Dates or numbers look different: Excel may apply its own display format or interpret values according to regional settings. Compare the actual cell value with the database result, and preserve identifiers as text where exact characters matter.
- The export is unexpectedly huge: Confirm that you selected the intended table or query. Add SQL conditions and remove unused fields before exporting instead of relying on cleanup in Excel.
XLSX or CSV: which should you use?
Choose XLSX when the recipient needs an Excel workbook, when multiple worksheets or cell types matter, or when you want a file that opens as a workbook without first importing a delimited text file. XLSX is also useful when the data needs to be reviewed alongside workbook formatting or formulas added after export.
CSV is often preferable for a simple, portable text export or a very large dataset that does not fit on a worksheet. A CSV file does not preserve workbook formatting, multiple sheets, or Excel cell types; it stores delimited text. When opening CSV in Excel, automatic conversion can affect dates, leading zeros, and long numbers. Importing the text and explicitly choosing column types is safer when those values must remain exact.
Neither format should be treated as a perfect record of database semantics. If the receiving system needs exact types, constraints, or a reliable machine-to-machine transfer, use an appropriate database or data-exchange format instead of assuming an Excel file is a database copy.
Frequently Asked Questions
Can DBeaver export a SQL query directly to Excel?
Yes. Run the query, right-click its results grid, choose Export Data, select XLSX, and complete the wizard. The workbook contains the query result, not a live link to the database.
Does DBeaver export to .xlsx or .xls?
The Excel option is commonly presented as XLSX or Excel 2007–365, which produces the modern .xlsx workbook format. Check the format name and file extension in your installed version rather than assuming it creates the older .xls format.
Can I export only selected rows or columns?
For precise control, write a query that selects the required columns and filters the required rows, then export that result. This is more dependable than exporting an entire table and deleting unwanted data afterward.
Why are leading zeros missing in Excel?
Excel may interpret a code as a number and discard its leading zeros. Treat the field as text in the query or export where possible, and verify the result in the workbook. This matters for codes and IDs, not just visually formatted numbers.
Can DBeaver export more than one million rows to one Excel sheet?
No single Excel worksheet supports more than 1,048,576 rows. Filter or divide the data into batches, or choose a format intended for larger tabular exports. Confirm the DBeaver transfer behavior rather than expecting automatic splitting.
Will editing the Excel file update the database?
No. The exported workbook is a snapshot. Editing or saving it does not write changes back to the database; use DBeaver’s database editing or an appropriate import workflow if data needs to be changed.
Related
- How to Add the Copilot Icon in Excel
- Convert XLS to Excel: How to Save as an XLSX Workbook
- Convert XML to Excel: Import, Clean, and Save Data
Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.
More in How-to basics
- How to Delete a Blank Page in Word Without Losing TextTo delete a blank page in Word, turn on formatting marks with Ctrl+Shift+8 on Windows or Command+8 on…
- Delete a Hidden Row in Excel: Safe Steps That WorkTo delete a row that is hidden in Excel for Microsoft 365 on Windows, enter its row number…
- Compare Two Excel Sheets for Differences: A Practical GuideTo compare two Excel sheets, use a cell-by-cell formula when the same records occupy the same positions, or…
- Put Currency in Google Sheets: Format Cells and ConvertTo put currency in Google Sheets, select the cells, then choose Format > Number > Currency. To choose…
- Excel Day Trading Journal: Build a Useful Trade LogYes—Excel can track day trades, calculate profit and loss, and help you review whether your strategies and rules…
- Excel Shortcut Keyboard Mat: What It Is and How to ChooseAn Excel shortcut keyboard mat is a desk pad or large mouse mat printed with keyboard shortcuts for…
Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources
Spotted an error in this guide? Let us know.