Use of PL/SQL Developer in a "live" environment

[SiDude]

Hi Folks,

I'm new here though I've been using PL/SQL Developer for about 5-6 years and I love it.

Just after your opinions on the use of this tool as a Live Support tools. I know its actually a development IDE and very usable and feature ladden one at that, but does anyone use this in a live environment? If so, what has been your experience?

It has obvious benefits but at the same time has its disadvantages.

The camps split where I work and I'm just looking for the opinions of people outside of this organisation.

So - how do you use yours ?

Thanks in advance

 

[ScottMattes]

one of my co-workers uses PLSD to access our production environment - he hasn't mentioned any problems.

in development we all have pretty much unlimited rights, but in production we have only select.

 

[SiDude]

Thanks for the reply.

I suppose it depends on how strict your company is. We're quite restricted.

We've had problems with locked tables in production because someone was using the tool incorrectly etc plus the old chestnut of its not really audited running on Windows etc as opposed to doing something via SQL Plus. DML activity is hidden by the tool making it harder to determine whats going on (such as locked tables) at the database level so I'm told.

Don't get me wrong, None of this is the fault of the tool its just how its used. I was just wondering how other people cope - or if they just don't bother as its a Dev tool.

 

[rbrooker]

i have used PLSD on production for about 9 years ( since 1.61! ), not had any issue with it that i havent had with other tools ( including sqlplus )...

 

[Marco van der Linden]

I have been using PL/SQL Developer now for 6 or 7 years and in all shops I have worked it has been used against a production environment.
Depending on the security policies (and my job description) I could either access the production environment logging on as a read-only user or as the application user (Oracle APPS in my case).

The only advise I can give is, make sure you don't give rights to some flashy manager who has been reading 'SQL for Dummies' and decides he's 'ready' to build his own ad-hoc reporting SQL.