True. You could however, (for < 10g), incorporate the appropriate parts into scripts named prompt.sql and connect.sql (or use 10g client). When connecting from sql prompt SQL > @PROMPT or @CONNECT . connect.sql could call prompt.sql automagically. @connect prompts you from username password etc. @prompt is if you are already connected... sets the prompt. Really 10g obsoletes all this so you could install 10g client and all can be set from glogin.sql. Then you can connect from one database to another and your prompt will change automagically even if you are connecting to Oracle 9 databases. Joel Patterson Database Administrator joel.patterson@xxxxxxxxxxx x72546 904 727-2546 ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jared Still Sent: Monday, September 10, 2007 1:26 PM To: tanel.poder.003@xxxxxxx Cc: Michael.Coll-Barth@xxxxxxxxxxxxxxxxxxx; oracle-l Subject: Re: SQL*Plus Client on Windows On 9/8/07, Tanel Poder <tanel.poder.003@xxxxxxx> wrote: Here's my i.sql which I use both for identifying where I'm logged on before doing any changes to database, plus it is called through login.sql. The window title change happens on the last line: There is one small problem with that approach: If you use 'connect' within sqlplus, and sqlplus is < 10g your title will not change, and you may become confused as to which system you are really on. One way around that is to use a wrapper for connect. Another way is to never use 'connect' from the command line, just exit and restart sqlplus with the new connection. -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist