Tidal Migrations is now Tidal!


December 2020 Newsletter, Tidal

Tidal feature releases and announcements in the December 2020 newsletter.

clouds clouds
December 2020 Newsletter, Tidal

Huzzah! You succeeded in remaining a human being this year! If you’re still feeling like this guy after the strangest year in decades, wrap yourself in blankets next to the nearest mountain of rich holiday treats and let the sweet world of the cloud take you into a new one.


Thankfully, 2020 was a big year for us at Tidal. Feature-wise, we bookended the year with a PDF Portfolio Report in January and an interactive Portfolio Insights feature in December.

What else is new? Well I’m glad you asked…


Also in 2020, we doubled our team of Migration Hackers, with team members from Halifax, the US, Australia (Kangaroos) and Austria (no kangaroos).

We’ve been super fortunate to bring three new crew members on board this month, and they just happen to be awesome. A huge welcome to Ehren Duisberg, Pranav Malaviya, and Sam King!


If you’re looking to fill your calendar for January, never fear - our next All-Virtual Migration Enablement Workshop is on for January 19, 2021! Register now and join us from home while our own David Colebatch walks you through the first 3 phases of the cloud migration process.

Can’t wait? You can sign up for a one-on-one if you like the sounds of a dedicated, private workshop, with our team.


“Hey David, I’m getting some push-back from our team regarding analyzing our production databases, the DEV databases should be enough, right?” - Terrance from the United States

Thanks Terrance and I wish that this was an unusual question, however, the fear of impacting production applications and databases with analysis is common.

While it’s true that you should protect your production workloads, it shouldn’t be irrational, in other words, it’s important to understand and determine if there will be any impact on the performance of the production database by performing the analysis.

It is also completely understandable to do a dry run on the development database to see what data would be collected, or evaluate any impact. But, when it comes to planning the migration of the production databases, it’s imperative that you evaluate the production databases, and not use dev as a proxy for prod.

Things like number of connections, disk I/O, the number of integrations, different features and permissions that have accrued over the years will be drastically different between development and production and furnish essential data to plan your migration.

Terrific question Terrance, keep them coming!




To fill that extra downtime you’ve planned, we’ve done a bit of a roundup of some news from 2020 that we thought was worthy of re-note!

That’s all for 2020. Thanks for your friendship this year, and as always, if you’ve had a good time with us this newsletter, let us know by sharing on social media (links below) and keep your friends up to date.

And in case you missed it, check out our November newsletter.

Stay united and see you in 2021!