Re: Force users to use Active DG for reporting

  • From: Andy Wattenhofer <watt0012@xxxxxxx>
  • To: ricard.martinez@xxxxxxxxx
  • Date: Wed, 2 Apr 2014 12:52:13 -0500

There are a lot of elaborate solutions being suggested. If you develop a
special elaborate solution for this, you're opening the door to a legacy of
supporting what is in effect an elaborate hack. Unless you're looking for
more job security, I would run away from anything like that.

Access plus ODBC is a hack-ish setup to begin with. So I would propose an
appropriately hack-ish solution: link all the RO tables and add the prefix
"reporting" to their linked names, and pre-pend the RW table names with
something scary like "OLTP". Instruct users to use the reporting tables
when they want to run reports, and likewise OLTP for data entry. Regardless
of whether they are running reports or entering data, they use the same
Access file. The barrier of having to think about which Oracle database
they are connecting to is removed.

Andy


On Mon, Mar 31, 2014 at 10:55 AM, Ricard Martinez <ricard.martinez@xxxxxxxxx
> wrote:

> Hi list,
>
> We got an environment formed by one standalone 11g database (lets call it
> RW)  with an active dataguard on another server (lets call it RO)
> We have provided to the users 2 tnsnames, one pointing to RW and the other
> to the RO, and we have told them to use the first one for DML, etc and the
> RO only for runing the reporting statments.
>
> As good users, they just ignore us and run all on the RW database, so we
> want to force them to use the RO for reporting.
> Meanwhile they got the 2 tnsnames entries, i see no real options to force
> them to use the RW, unless we separate the schema in two (one with
> insert/update, the other only with select), and we kill any session of the
> select schema on the RO (using a cron  maybe, forcing them to use RW to be
> able to end their reports)
>
> Has any of you found in a similar situation, or can think in other options?
>
> Thanks
>
>
>
>
>
>
>


-- 
Andy Wattenhofer
Manager, Database Administration
University of Minnesota

Other related posts: