Multiple users can't share a local temporary table because it is local to one user session. A global temporary table, also exists for the duration of a user session or the procedure that created the table.You also can't grant or revoke permissions on the local temporary table. When the last user session that references the table disconnects, the global temporary table is lost.
However, Sphinx does not depend on nor require any specific database to function.
Applications can access Sphinx search daemon (searchd) using any of the three different access methods: a) via Sphinx own implementation of My SQL network protocol (using a small SQL subset called Sphinx QL, this is recommended way), b) via native search API (Sphinx API) or c) via My SQL server with a pluggable storage engine (Sphinx SE).
In this step by step tutorial, I am using Adventure Works database from Microsoft.
This database was created for testing purpose and is ideal for our example.
Local and global temporary tables differ in a subtle way.
Let's look at what SQL Server says about temporary tables.Third party API ports and plugins exist for Perl, C#, Haskell, Ruby-on-Rails, and possibly other languages and frameworks.Starting from version 1.10-beta, Sphinx supports two different indexing backends: "disk" index backend, and "realtime" (RT) index backend.Instead, you must create that represent the XML data of interest, and then use those virtual columns to define the constraints that you need.This approach applies only to XML data that is stored as binary XML.XML developers can leverage the power of XML standards while working in the context of a relational database. That is, individual XML elements and attributes are not mapped to individual database columns or tables.