Re: exporting data from one DB to another asynchronously

>
> Nagita, why do you want two databases?  under normal
> circumstances, you'd just use one db to store your
> data and your application would run a SQL statement
> against it in order to pull the relevant data.

I want to keep my three applications as separate as possible so one
application can't possibly access information in another.

I am leaning towards putting everything on one database using
different schemas to keep the data separate.

> if you *really* want to keep the data separate
> (security reasons, for example), it is best to design
> the schemas (or dbs) that way and use your application
> to enter the data into both dbs (real time, not
> transfer stuff all over the place), but only make the
> "public" data available to the dbuser defined in the
> app to run the sales survey.
>

That seems like a good idea. Possibly simpler too.

> i've never done this, so don't assume what i just said
> necessarily makes sense, though.  ;-)
>
> come to think of it, you could probably manage
> prmissions on tables to achieve the same result,
> should that be a requirement.

Like giving permissions to each app to specific tables. I guess that
would be good as well.

> good luck.
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>