Okay, we have a request for quite a few of our customers for read-only
copies of their databases they can do their ad-hoc queries on. These
read-only databases need to as closely matched to the production
database as possible, i.e., exact, from their point of view.
I've looked into some options
Walt,
I presented a paper at IOUG Live 2003 and wrote an article on DBAZine on an
issue similar to this. Although the issue addressed was something much more
complex; the article does have scripts to set up a basic readonly snapshot
(or MV) replication. The article is at
I have attached some generic scripts for creating the snapshots and
refresh procedures. The only item missing is the database link.
Basic outline:
1. create database link
2. create snapshot logs on primary
3. create snapshots on copy
4. run a full refresh
5. run a fast refresh
6. setup jobs with
Weaver, Walt scribbled on the wall in glitter crayon:
Okay, we have a request for quite a few of our customers for read-only
copies of their databases they can do their ad-hoc queries on. These
read-only databases need to as closely matched to the production
database as possible, i.e.,
: A basic replication question
Weaver, Walt scribbled on the wall in glitter crayon:
Okay, we have a request for quite a few of our customers for
read-only
copies of their databases they can do their ad-hoc queries on. These
read-only databases need to as closely matched to the production
ad-hoc queries
as in, we'll write something that will bring your database to its knees
that kind of reporting, it's better to have a separate database
--- Thater, William [EMAIL PROTECTED] wrote:
Weaver, Walt scribbled on the wall in glitter crayon:
Okay, we have a request for quite a
Some issues to think about here:
Do they really need all the data from production?
Or are they just saying that without any justification...
Do they know what questions they are going to ask?
Or is this a fishing expedition.
Are they going to understand ad-hoc development will continue to not
