I'm trying to think through a setup with a central mariaDB instance (A) accessing data on physically remote servers (B).

All queries to the database (A) can be answered from indices only. Indices are read-only that is re-indexing is triggered from the remote-server (B) at certain intervalls (once per day).

I'm far from a specialist in database things, so when searching around and finding mariadb CONNECT I was wondering:

Is it at all possible to have a mariaDB database (A) containing "indices only" and the underlying tables being kept on remote locations (B)? If it was, is it feasable?

Thanks for some ideas!

  • 1
    I have one question for you: WHY?
    – Philᵀᴹ
    Mar 2, 2015 at 20:56
  • Hm. Data will be kept and maintained in the remote location, so I was thinking if it was possible to keep it there and still have "something" query-able like an index - says me, the "database-whitebelt"
    – frequent
    Mar 2, 2015 at 21:04
  • An InnoDB table is just an index anyway, so a table + N indexes is just (N+1) indexes. Why not just use plain old replication? Think of the table as just one additional index (which it is!) Mar 3, 2015 at 10:16
  • ok. I got the point in terms of feasability. Now would it be technically possible?
    – frequent
    Mar 3, 2015 at 12:24

1 Answer 1


No: local instance can't know when remote tables are updated.

Also, I suggest you use SPIDER instead of CONNECT.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.