Moving from Sequel Pro to Sequel Ace

Moving from Sequel Pro to Sequel Ace
Sequel Ace is the "Sequel" for Sequel Pro, why and how to move from Sequel Pro to Sequel Ace.

Published by Rick Daalhuizen

Introduction

Sequel Pro is an open-source SQL Client for MacOS, and for many Developers (myself included) the must-have tool when dealing with a SQL server. It’s fast, has an easy interface, and is very intuitive to use.

You may have noticed that in recent years little has changed in terms of features and how it looks. After some recent updates in MacOS, I keep running into new bugs in Sequel Pro:

It’s also not surprising when you consider that the last release was Sequel Pro - 1.1.2 on April 3, 2016 . Looking at the commit on their Github page it has only gotten less in recent years.

Sequel Pro Github Contributtions

But now the good news! There is a replacement and that is Sequel Ace, or whatever they call it: “Sequel Ace is the” sequel “to longtime macOS tool Sequel Pro”. In addition, it is open source and available on the Apple App Store.

It is a fork of Sequel Pro so the interface remains largely the same, which makes switching to Sequel Ace even better.

Preparation

  • macOS >= 10.10
  • MySQL >= 5.6
  • MariaDB

# Installation

The easiest way is to install Sequel Ace via Homebrew

brew cask install sequel-ace

Now that it’s installed you can open it with ⌘ + spacebar and type in Sequel Ace

Sequel Ace Startup Screen

Import connections from Sequel Pro to Sequel Ace

The easiest way is to right click on export, and import this file back into Sequel Ace in the same way.

Sequel Pro Export connections

Another way is to copy your files that are in the ~/Library read: Migration from Sequel Pro to Sequel Ace

Connecting to SSH

Before we want to make an SSH connection from Sequel Ace, we need to give it access first. This was not the case with Sequel Pro. The reason for this is that Sequel Pro runs in sandboxed modes. This also gives an extra layer of protection.

For this we need to add our ~/.ssh/config manually.

If you don’t have one, make sure to create it first.

Here’s an example of an ssh config for my local warden (Docker) environment.

Host tunnel.warden.test
  HostName 127.0.0.1
  User user
  Port 2222
  IdentityFile ~/.warden/tunnel/ssh_key

Now go to: Preferences -> Network -> SHH config: Other file …

Select your ~/.ssh/config file.

Once you have added this you will see the file under: Preferences -> Files -> Available files.

When everything is setup right you can now connect to your SSH environment.

Sequel Ace Connection Succeeded

Ps: Sequel Pro uses as default port: 22 for your SSH port.

Conclusion

Hopefully, this has given you enough information on how to switch from Sequel Pro to Sequel Ace. If there are any questions or suggestions, let me know in the comments.