On Mon, 15 Jul 2002, John Moore wrote:
> This is how we did it at a previous employer. I was hoping somebody has
> some other trick, since we don't have any easy way to replicate the data!
Well, if you've got scheduled downtime every day, and can live with
once-a-day updates, you could always sh
At 09:04 PM 7/14/2002, Curt Sampson wrote:
>On Thu, 11 Jul 2002, John Moore wrote:
>
> > The issue is how to prevent users from hogging the system, and especially
> > from slowing down the on-line users.
>
>Mixing OLTP and OLAP on one database server has never seemed like a good
>idea to me. Part
On Thu, 11 Jul 2002, John Moore wrote:
> The issue is how to prevent users from hogging the system, and especially
> from slowing down the on-line users.
Mixing OLTP and OLAP on one database server has never seemed like a good
idea to me. Part of the problem with the idea of resource limitation
This is an issue that I have never seen we;; ved with other databases I
have used:
We have an on-line application that is PSQL based. Users want to be able to
get reports from this database - both canned reports that we might write
for them, and ad-hoc reports where they use an odbc-based repo
This is an issue that I have never seen we;; ved with other databases I
have used:
We have an on-line application that is PSQL based. Users want to be able to
get reports from this database - both canned reports that we might write
for them, and ad-hoc reports where they use an odbc-based repo
