Microsoft Flow could be a good tool to export information from multiple sources like an Azure SQL database. But you should check Azure Functions and Office Graph API as well. This couldn't be a solution if you are thinking in a non code solution but I think it could be great because of all the possibilities that opens up for logging, tracing, checking and so on.
Microsoft Flow allows you as a user to create workflows but not as a system account. Think of this restriction when choosing the tool, that's an important point.
Talking about the solution:
Your solution must have a modified date for each item in the SQL database to know the las rows that have been modified. You must have a control table to save the time of the last iteration. Having these two dates you will be able to update the rows that have been affected in SharePoint. This solution didn't check the deleted rows so you should think on a better solution.
Another approach could be delete all items in SharePoint and create all new items from the SQL. The problem here will be the time on deleting and creating again all these items. The search engine will be affected as well. It will crawl the 80k items each day and update the index for those 80k items plus the 80k items removed.
Hope this can help you.