MySQL can do the analysis you need with the right indexing (I have worked with 100m+ row analytics in MySQL) but a columnar database as others have mentioned wo

MySQL can do the analysis you need with the right indexing (I have worked with 100m+ row analytics in MySQL) but a columnar database as others have mentioned would be better, as would a columnar version of MySQL like infobright or infinidb. (At one former firm we switched from mysql to infobright for some jobs due to significant speed benefits working with hundreds of millions of rows while retaining backward compatibility with our code base.) (Although for string searches if you want fuzzy search you might be better off with ElasticSearch/Lucene than a relational database.) As for delimiters, escape characters, bad characters (and character sets and collation settings) and import/export techniques, these exist across databases. If the data were clean, analytics would be a quick and easy job, but it rarely is; that challenge is kind of the nature of the problem domain.