{"id":45691,"date":"2026-09-21T03:40:00","date_gmt":"2026-09-21T03:40:00","guid":{"rendered":"http:\/\/www.withdata.com\/blog\/?p=45691"},"modified":"2026-09-21T15:31:41","modified_gmt":"2026-09-21T15:31:41","slug":"redisdatastudio-2-1-released","status":"publish","type":"post","link":"https:\/\/www.withdata.com\/blog\/pr\/redisdatastudio-2-1-released.html","title":{"rendered":"RedisDataStudio 2.1 Released: Export Redis Data to Relational Databases"},"content":{"rendered":"

September 21, 2026 \u2014 Withdata Software announces RedisDataStudio 2.1<\/a><\/strong>, a cross-platform desktop tool for editing, importing and exporting Redis data. This release adds exporting Redis data to relational databases \u2014 including creating new tables and running exports from the command line \u2014 and improves importing from databases, Hash\/JSON handling and the Redis key list.<\/p>\n

\"RedisDataStudio<\/p>\n

What\u2019s New in RedisDataStudio 2.1<\/h2>\n

1. Export Redis Data to Relational Databases<\/h3>\n

RedisDataStudio has always been able to edit Redis data and move it to and from files. Version 2.1 adds the missing direction: exporting Redis data into a relational database<\/strong>. Pick the Redis keys you want and send them to a table in MySQL, MariaDB, PostgreSQL, SQL Server, Oracle, SQLite, Access, DB2 and more \u2014 no scripting required.<\/p>\n

You can export a single key, a set of keys, or a whole namespace, across all five Redis types (String, Hash, List, Set and Sorted Set), with automatic field mapping between the Redis data and the database columns.<\/p>\n

2. Export to a New Table<\/h3>\n

You don\u2019t need to create the target table first. Choose \u201cnew table\u201d and RedisDataStudio creates it for you, inferring the columns and their data types from the source keys, then loads the data. This makes \u201cdump this Redis data into a database\u201d a one-step task.<\/p>\n

3. Command-Line and Scheduled Export to Database<\/h3>\n

Database export works from the command line too. A saved session can be run headless with RedisDataStudioCmd, so you can export Redis data to a database on a schedule \u2014 the same way file exports already worked.<\/p>\n

4. Improved Import from Relational Databases<\/h3>\n

Importing from a database has been fixed and improved: the source selection (a single table, a query, similar tables read as one, or multiple tables) now works as expected in every case.<\/p>\n

5. Improved Hash and JSON Columns<\/h3>\n

When a Hash key stores JSON objects, RedisDataStudio can expand them into columns. The column set is now built from a sample of records and the union of their JSON keys, instead of just the first record \u2014 so records with slightly different shapes are no longer truncated. The sample size is configurable, and \u201cValue (JSON) As Columns\u201d is now detected and enabled automatically when a value looks like JSON.<\/p>\n

6. Improved Redis Key List<\/h3>\n

The key list now shows the correct keys for the selected type, tells you how many keys are loaded and whether more are available, and remembers the \u201cShow Keys In Namespace\u201d choice. Finding and selecting the keys you want is quicker, especially on a server with many keys.<\/p>\n

About RedisDataStudio<\/h2>\n

RedisDataStudio<\/a> edits Redis data and moves it between Redis, files and relational databases \u2014 fast, locally, and without coding.<\/p>\n