Potentially about anyone who used Access without the forms interfaces... While I'm not the biggest fan, I know a lot of people who prefer a visual editor for table schema creation. They'll use SQL Management Studio, or whatever equivalent with other DBMS and edit that way instead of DB specific queries... For example, re-ordering fields is destructive in a lot of DBMS and the queries get painful, a visual editor eases this burden.
As to importing/exporting data (csv, etc), You can't exactly run queries against a CSV generally (I mean you can with JET/ODBC, but still)... it's a chore.
To another point, I often feel that sqlite is a great backup format for data, it's portable, you can query directly, etc. I kind of wished that Azure Data Studio (now discontinued) had directly supported loading CSV/TXT etc into an in-memory or temp db for queries and portability similar to mentioned between various data sources (sqlite, mssql, pgsql, etc).
>kind of wished that Azure Data Studio (now discontinued) had directly supported loading CSV/TXT etc into an in-memory or temp db for queries and portability QStudio supports right click query csv,txt,parquet via duckdb. It also supports more exotic data sources like rest apis by placing the data into a temp table. I called it babeldb https://www.timestored.com/qstudio/csv-file-viewer