Re: Team coding in TOAD and SQL Navigator

since both are client tools, neither technically exists 'in an instance' -- both tools simple connect to one or may schemas in one or more instances (on my current project I'm typically connected to 4 schemas in 3 instances on 3 separate machines)

so, short answer, yes they can co-exist, quite nicely

i've used SQL Navigator a bit, but prefer TOAD -- the TOAD interface is much cleaner, although Quest is starting to muck it up a bit. SQL Navigator's interface reminds me of AOL's -- just too much going on

a problem you'll need to address in both environments in version control -- either through a tool integrated with TOAD or SQL-Nav, or via data-base centric techniques (i can pass on some info on some DB triggers and package techniques that can help in this area)

-- 
Mark C. Stock
email mcstock -> enquery(dot)com
www.enquery.com
(888) 512-2048


"H?kan Granstedt" <hakan.granstedt_at_astrazeneca.com> wrote in message
news:9065aab1.0311120140.251590d0_at_posting.google.com...


> Do you have any experience with Team coding in Toad or SQL Navigator?

> Any difference between them? Can they coexist in the same instance?

>

> Håkan Gransted