What one dbSlice license covers
- Migrate
Initial load between any two of the leading databases, with the target DDL shown first.
Migration guides → - Keep in sync
Upsert, New rows only, Update existing only or incremental by column, in batch, on a schedule.
Data coexistence → - Automate
Save any run as a job and run it from the command line, on any scheduler, with e-mail and webhook alerts. The Linux edition adds a built-in scheduler and a job API.
Sync from the command line → - Prove
Compare source and target key by key and save the full list of divergent keys to a file.
Compare source and target → - Mask
Obfuscate sensitive fields in flight, with keys and foreign keys preserved.
Masked staging copies → - Test data for DEV and QA
Fill tables with synthetic rows, with foreign keys filled from values that exist in the referenced table, without copying production.
Synthetic data →
Best tools by database pair
- Best tools to migrate SQL Server to PostgreSQL
- Best tools to migrate MySQL and MariaDB to PostgreSQL
- Best tools to migrate SQL Server to MySQL
dbSlice and…
- DBConvert
Better choice when: You need sources dbSlice does not read (Access, DB2, FoxPro, Excel, InterBase), tables, views and foreign keys converted in the same product, or CDC with DBConvert Streams.
Read the comparison → - Full Convert
Better choice when: You run one very large one-time migration, need sources dbSlice does not read, or want the whole target schema created in one tool.
Read the comparison → - SQLines
Better choice when: You convert a lot of PL/SQL or T-SQL, or need sources such as IBM DB2, Informix or Sybase.
Read the comparison → - EMS Data Pump
Better choice when: You import one way into a single target engine, qualify for individual or non-profit pricing, or use the EMS family on the same engine.
Read the comparison → - pgloader
Better choice when: You make a one-time move into PostgreSQL, including the schema, and want a free, open source tool.
Read the comparison → - DBeaver
Better choice when: You want one database tool for daily SQL work (browse, query, edit) and an occasional copy of tables between databases, which the free Community edition covers.
Read the comparison → - Microsoft SSMA
Better choice when: You move into SQL Server or Azure SQL and need the code converted.
Read the comparison → - AWS DMS
Better choice when: The target is in AWS and you want AWS to run the infrastructure, or you need continuous change replication with low lag.
Read the comparison → - Redgate SQL Data Compare
Better choice when: Everything you run is SQL Server, or you compare against backups or scripts in source control.
Read the comparison →
Many teams use dbSlice next to one of these: a code conversion tool for procedures and views, dbSlice for the data and the sync until cutover.
What touches your data
dbSlice runs where you put it: your Windows machine or server, or your own Docker. It reads the source by key in small batches and writes only rows to the target. By default it creates nothing in your databases, and dbSlice never sends database rows to Thinwork. If an unexpected error happens, you can choose to e-mail the details to support: you see the text before you send it.
Your network
By default, nothing is created in your databases: no triggers, tables or agents. dbSlice never sends database rows to Thinwork.
Leaves your network
- license activation and renewal
- update check and download
- release notes list
- an error report e-mail, only if you choose to send it (you review it; an error text may quote a value)
- e-mail (SMTP), webhook, REST API
- SOAP (and its WSDL), gRPC, broker
- your telemetry collector
The honest con about dbSlice
- dbSlice moves data. It does not convert stored procedures, triggers or views.
- It runs batch jobs, on demand or on a schedule, not real-time replication. Incremental runs do not see rows deleted at the source, so run Compare or a reload before the switch.
- It is a Windows app with a command line. The Linux edition runs in Docker on your own infrastructure.
How we write these pages
- Facts about other tools come from their own websites, with the date we checked them on each page.
- We recheck prices every month.
- We say where the other tool is the better choice.
- If something on a page is out of date, write to us (support@dbslice.net) and we fix it.
Who builds dbSlice
dbSlice is built by Thinwork, a software company in business since 2007. It started as the internal tool behind our own work, rolling out Thinwork's ERP and running data projects for large corporations. For more than six years it has moved data in mission-critical production environments, on SQL Server, PostgreSQL, Amazon Aurora and InterSystems Caché/IRIS.
A small team at Thinwork, led by Junior Oliveira (40 years in IT): development, QA, finance and marketing, plus specialists brought in for specific projects.
Every e-mail is read by the people who build dbSlice. Questions before you buy? Write to support@dbslice.net. About Thinwork and dbSlice →
Planning a system replacement and need help designing the coexistence? Thinwork can run the project with you.