OK... more context, then (just for fun, though... doesn't really have anything to do with the question):

We've got a system that has a large number of identically structured databases. Because they are identically structured, then you can imagine a sort of "virtual database" consisting of the sum of all the constituent databases. For example, if you had a table FOO in each of the databases like: 

(
  FOOID       number,
  FOOTYPE     varchar,
  AMOUNT      number

[download]
for example. Thus, in the virtual database, there would exist a virtual table FOO like: 
(
  FOOID       number,
  FOOTYPE     varchar,
  AMOUNT      number,

[download]
  DATABASEID  number
)

[download]

So, if you took a query like: 

select sum(amount), footype
from foo
group by footype

[download]
and ran it against the virtual database, what would actually happen is that the query 
select sum(amount), footype
from foo
group by footype

[download]
would get run in parallel through all of the identical (actual) DBs, and they would each return their result sets to the virtual DB, which would then roll up the individual result-sets into one result set. It's conceptually as though the query were executed like: 
select sum(sum_amount), footype
from (
    select sum(amount) as sum_amount, footype
    from db1.foo
    group by footype
    UNION ALL
    select sum(amount) as sum_amount, footype
    from db2.foo
    group by footype
    UNION ALL
    ...
    UNION ALL
    select sum(amount) as sum_amount, footype
    from dbN.foo
    group by footype
)
group by footype

[download]
Only with the "UNION"s being executed in parallel.

To get an even better idea, there's stuff like: 

select sum(amount), footype
from foo
where databaseid in (1,2,3)
group by footype

[download]
This would get pulled apart, such that the "where databaseid in (...)" was removed from the query, and was used, instead, to control the set of databases over which to run the query.

Anyway, none of that is what I want help with. It's already a done deal... I'm trying to figure out if there are any tools, etc, on how to build an ODBC server interface... I've already got the server to back it up, I just need the ability to slap an ODBC access method onto it. 

------------
:Wq
Not an editor command: Wq

[download]

In reply to Re^2: Resources for building database *server* interface by etcshadow
in thread Resources for building database *server* interface by etcshadow

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.