William:
Check my old post.
"I agree with that Matthew.
But if you still have to use the link make sure you give the user the
appropiate provileges and
assign him a "profile" to limit the ammount of resources he can consume with
his queries.
This way he can't slow down the prod instance
On Tue, 15 May 2001,Rocky Welch scribbled on the wall in glitter crayon:
->How about creating a user that only has read-only rights?
But that still allows the "query from hell" syndrome that can bring a prod box to it's
knees.
--
Bill Thater Certifiable ORACLE DBA
Telergy, Inc.
My concern with that would be the performance aspect. Giving someone access
to run un optimized queries in Production could affect the overall response
time. I would not allow it personally, plus if you allow it for one ,you've
set a precedent
Sam
- Original Message -
To: "Multiple recip
Dennis,
We use DB links to allow selects where data info is needed on two instances. One is a
report type and the other is being updated by the users all day. They work great. To
keep the table naming simple and allow the application to be written on one
development instance, I use synonyms to
Well, you could create a user in the production database that only has
select privileges and then create the database link to access that account.
The big thing you'd have to be careful of here is that the person doesn't
try to run some crazy query that bogs down the production system (but you
c
How about creating a user that only has read-only rights?
--- [EMAIL PROTECTED] wrote:
> One of our development DBAs suggested today to build a private database
> link between production and test database so that he can run some
> queries against both at the same time. I am a little concerned bec
hater,
William" To: Multiple recipients of list ORACLE-L
<[EMAIL PROTECTED]>
Subject: Re: DB Link Betwee
Title: RE: DB Link Between Prod and Test?
I agree with that Matthew.
But if you still have to use the link make
sure you give the user the appropiate provileges and
assign him a "profile" to limit the ammount of
resources he can consume with his queries.
This way he can'
Title: RE: DB Link Between Prod and Test?
Is he an idiot? (I couldn't resist)
We go to extreme lengths
to ensure that nobody can link
our devlopement and production databases
together in any shape or form. It's just a bad
idea.
R. Matt Adams - GE Appliances - [EMAIL
Title: RE: DB Link Between Prod and Test?
I created a 'READER' id on production for our datawarehouse guys. The dblink connects from dw to production as user READER, and READER has select authority on the specific prod tables that they are supposed to be looking at.
DW has mu
On Tue, 15 May 2001,[EMAIL PROTECTED] scribbled on the wall in glitter crayon:
->One of our development DBAs suggested today to build a private database
->link between production and test database so that he can run some
->queries against both at the same time. I am a little concerned because he
abase Administrator
[EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 15, 2001 13:26
> To: Multiple recipients of list ORACLE-L
> Subject: DB Link Between Prod a
One of our development DBAs suggested today to build a private database
link between production and test database so that he can run some
queries against both at the same time. I am a little concerned because he
might make a mistake and accidentally corrupt the prod database. Anybody
out there who
Can he be trusted NOT to run some horrible query that would bring Prod to its knees?
>>> [EMAIL PROTECTED] 05/15/01 03:00PM >>>
If all he needs is select he cannot corrupt the DB if the DBA does not grant
unnecessary privileges. Folks
use dblinks all the time.
Rick
-Original Message-
Se
If all he needs is select he cannot corrupt the DB if the DBA does not grant
unnecessary privileges. Folks
use dblinks all the time.
Rick
-Original Message-
Sent: Tuesday, May 15, 2001 2:26 PM
To: Multiple recipients of list ORACLE-L
One of our development DBAs suggested today to build
15 matches
Mail list logo
