not sure why you think this? You still have to have some state (you cannot just rehydrate state of file system upon restart and keep everything in mem). To rephrase, those who don’t understand databases are bound to reimplement them…poorly. Why you think upgrade of metadata schema in those files will be less of an issue on upgrades (surely this will happen, file format will change, just now without constraints, foreign keys, checks and with manual reindexing and manual query optimizations)?

What is your latency? Can you move data closer to where db is (cloud)? Did you change isolation level? Or recovery model? Did you try bcp? Any indexes you have in table should be deleted?

Licence is compatible, but data they have is of…questionable quality…to say at least. For example, I think building dataset is Odbl and I think it contains ML-detected buildings. These got released years ago (becase they had to release it as OdbL to mix them in their maps). Rarely who imported these buildings in OSM as there are lot pf false positives and what not. So, just because they released something under odbl/cdla doesn’t mean it is good for OSM and that it could be imported (for example speed profiles, if we ever get real gold data). Overture is more of a playground for big tech to play without OSM telling them what is good and what is not

OsmAnd works on iOS too