>based on comments I see, MS SQL Server users are a minority here,The issue isn't that he's mentioning a specific tool that a minority uses. It's that his solution isn't even appropriate for the gp's scenario that had these 2 desirable properties:
(1) send one file
(2) the file is queryable (with SQL language)
I never downvote pjmlp's posts but the following type of comment isn't just opinionated... its tone will also be perceived as condescending:
- "I do exactly the same with traditional RDMS. Export to single file isn't nothing new."
So to entertain that suggestion, what single file would MS SQL Server export?
option A: Let's say we export to a single text CSV. Ok, we now satisfied the single file property -- and that's if we pre-join all relational tables into a diskspace-hogging output where columns repeat redundant denormalized data. But text files are not easily queryable. You either have to re-import into another tool that can run SQL commands or import into Excel to play with filters.
option B: Let's export to single MDF file. Now we're asking recipients to have MS SQL Server installed and ATTACH the mdf file.
The above "MS SQL Server solutions" are more complicated than a single SQLite file queryable with a zero-install Sqlite CLI utility.
But hey, offering up "alternative solutions" with a condescending tone is regular sport for HN so I guess we all roll with it. (https://news.ycombinator.com/item?id=9224)