5 ms·

is memSQL a replacement for a full RDBMS in your stack ? Or just for analytics -- siphoning off the data from your master.

ryanworl 8y ago
MemSQL is an "HTAP" (hybrid transactional-analytical processing) database. They have an in-memory row store table engine for the transactional queries and a disk-backed column store table engine for the analytical queries.
deleted 8y ago
[deleted]
nikita 8y ago
Yes we have customers that standardize their database workloads on memsql and move off of oracle
CuriouslyC 8y ago
Personally, I would not use memsql as a first line RDBMS. It lacks too many useful features, and it doesn't return consistent results for all queries (I've found inconsistencies when using group by with having, for instance).
- ruw1090 8y ago
  If you have an example of the query you thought was returning inconsistent results, feel free to make a post over at https://www.memsql.com/forum/ https://www.memsql.com/forum/ with a repro.
- gacba 8y ago
  Been using MemSQL for a enterprise-level financial services client since mid-2017. We have this in production and are running it in a multi-TB cluster. We've not seen ANY of these issues here and are heavy, crazy query users. Their support has been nothing but on-the-spot and very helpful.
  - CuriouslyC 8y ago
    I totally admit that the inconsistency might be a result of misconfiguration by maintainers at my company. That being said, being able to shoot yourself in the foot so subtly and badly via configuration seems like a pretty strong anti-feature.
    - manigandham 8y ago
      Since you aren't sharing any actual details and are switching between blaming the product to blaming your devs and config (where no product can magically keep you from breaking settings), your comments come across as rather disingenuous. Why not share a clear example of exactly what happened, or post on their forum with details, so we can all judge for ourselves?
manigandham 8y ago
It can be, but if you're using the rowstore tables (best for single row lookups and constant modifications) then you'll have to keep all that data in RAM which can be limiting.

ryanworl 8y ago

MemSQL is an "HTAP" (hybrid transactional-analytical processing) database. They have an in-memory row store table engine for the transactional queries and a disk-backed column store table engine for the analytical queries.

deleted 8y ago

[deleted]

nikita 8y ago

Yes we have customers that standardize their database workloads on memsql and move off of oracle

CuriouslyC 8y ago

Personally, I would not use memsql as a first line RDBMS. It lacks too many useful features, and it doesn't return consistent results for all queries (I've found inconsistencies when using group by with having, for instance).

ruw1090 8y ago
If you have an example of the query you thought was returning inconsistent results, feel free to make a post over at https://www.memsql.com/forum/ https://www.memsql.com/forum/ with a repro.
gacba 8y ago
Been using MemSQL for a enterprise-level financial services client since mid-2017. We have this in production and are running it in a multi-TB cluster. We've not seen ANY of these issues here and are heavy, crazy query users. Their support has been nothing but on-the-spot and very helpful.
- CuriouslyC 8y ago
  I totally admit that the inconsistency might be a result of misconfiguration by maintainers at my company. That being said, being able to shoot yourself in the foot so subtly and badly via configuration seems like a pretty strong anti-feature.
  - manigandham 8y ago
    Since you aren't sharing any actual details and are switching between blaming the product to blaming your devs and config (where no product can magically keep you from breaking settings), your comments come across as rather disingenuous. Why not share a clear example of exactly what happened, or post on their forum with details, so we can all judge for ourselves?

manigandham 8y ago

It can be, but if you're using the rowstore tables (best for single row lookups and constant modifications) then you'll have to keep all that data in RAM which can be limiting.