SteemSQL - Database update and preparation for SMTs

SMTs are coming with the next hardfork and there will be a lot of new information available in the blockchain!

Since many processes in the Steem ecosystem rely on SteemSQL for their day-to-day work, it's better to be prepared than having to deal with downtime the hardfork will be rolled-out.

Therefore, I’m actively working on updating the SteemSQL database to prepare it for SMTs.

One stone two birds

As this preparatory work requires to review the entire structure of the database and its tables, I take this opportunity to make additional modifications to improve the performance of SteemSQL for (d)Apps and processes that use it.

Existing users of SteemSQL do not have to worry because I'm doing my best to preserve how the current structure is presented to third parties (you). This means that the changes currently made should not have an impact on the current functioning of your apps or processes.

Once this work is done, and before putting things into production, I will post an announcement to provide you with an exhaustive list of changes and to allow you a few days to make your own adaptations.

Sorry for the inconvenience

Delays in synchronization with the blockchain could occur.

If your applications rely on real-time data availability, which should not be the case because SteemSQL is not a tool suitable for this kind of processing, you may encounter some hiccups.

Indeed, given the huge size of the database (more than 1.5 TB) and the large volume of non-stop blockchain activity, it is sometimes necessary for me to stop the data injection process in order to be able to perform some changes. Data will still available, but no more updated.

These break times should not exceed the hour, but you never know, it could sometimes last a little longer. I'm doing my best to make it as short as possible and for SteemSQL to catch up quickly afterward.

The status of SteemSQL can be viewed on this page.