As long as the older clients do not cross a boundary backward regarding the securability of the sqlnet protocols, letting application needs drive this seems reasonable. More and more the clients are just machines to run browsers from the viewpoint of the database server, usually divorced yet another layer by application server or web server middle tiers that concentrate connectivity and load balance at the current primary database server farm site. Remote access directly to the database servers by just plain users is probably best constrained to a well controlled small group (I'm not ruling out zero here), and such groups are candidates to be kept near the bleeding edge of technology anyway. Very interesting thread to start Chris, and I look forward to hearing the broad perspectives of oracle-l on this. Your mileage may vary, mwf _____ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Taylor, Chris David Sent: Tuesday, May 18, 2010 12:11 PM To: 'oracle-l@xxxxxxxxxxxxx' Subject: Who pushes for client upgrades on workstations - DBAs or Development Group? I'm just curious how everyone feels about the need to upgrade Oracle clients and reasons for doing so in a typical environment. Do you, as the DBA, push for Oracle client upgrades, or do you let the Development group (and/or application upgrades) necessitate the upgrade? Personally, I've always been of the opinion to let application upgrades (for commercial software) and/or the Development Group to push as the PC/LAN group (those responsible for workstations) usually handle client installs etc. I have no problem supporting legacy clients (such as 8i) nor newer 11g clients. What are your thoughts? Chris