SQribe can be used by software developers, database administrators, and other IT professionals, to backup, restore, and archive local and remote Microsoft SQL Server database schemas and data from Windows, macOS, and Linux computers.
Local cloud database backups.
Cloud database services like Amazon RDS and Microsoft Azure SQL are a great innovation, but with the convenience comes the surrender of some control; like access to your backups. Sure, you can create your own restore points, but there’s no easy way to keep offsite copies.
With SQribe you get some of that control back. In one command it will generate schema and/or data scripts that you can put away for safe keeping. And the data can even be compressed!
Faster development cycle.
If you’re building web applications that leverage SQL Server, especially CMS platforms like Umbraco, DNN, Orchard, Sitecore, SharePoint, Sitefinity, and more, you probably need to wipe and restore your development database periodically. And the ability to do so from any computer (like a MacBook) would be even better.
SQribe makes it really fast and easy to wipe and restore your development database so that you can enjoy the art of breaking things, er, software development.
Easy database versioning.
You’re likely using git, subversion, or other version control system to manage your development process and ensure continuity, especially if you work in a team. But are you versioning your database?
If you use SQribe to version your database design, you can restore schema and/or data to a point in time just like you can with code. That means diff, merge, and other features the VCS tools provide will all work too, since SQribe uses T-SQL scripts for its backup files.
Databases on separate VPNs? No problem.
Many VPN client applications don’t play well together, making it nearly impossible to transfer a database across that boundary. A common scenario is needing to download a production database to refresh a local or staging database when both reside on separate VPNs.
The VPN barrier doesn’t affect SQribe because backup and restore activities are independent. You connect to the source and back it up, then connect to the second and restore. And if you need to wipe and restore as you build, you already have the files. Problem: solved.
- SQribe is a 64-bit native code CLI that works on Windows, macOS, and Linux.
- Multi-threaded for blazing speed; independently specify the number of threads to use for backups and restores.
- Backup SQL Server databases to specially crafted T-SQL script files which can be restored, versioned, or archived for later use.
- Restore SQribe backup files in one step.
- Optional ZIP compression for data backups.
- Chunk table data into fixed-size files for easy storage on removable media.
- Specify tables to ignore when backing up data; specify tables to leave untouched when restoring.
- Choose the database objects to backup and restore, like tables, stored procedures, extended properties, and more.
- Create settings files in a simple JSON format so you can run jobs over and over without tons of command line arguments; create your own defaults for backups and restores using the same JSON format.
- Free and open source under a GNU GPLv3 license.
Ready to check it out?
Visit our github account and clone the repository to check it out. If you'd like to contribute to the project, we'd love to have you! Just let us know.