RE: Preventing access to DB by Toad version
Bert Scalzo <[email protected]>
| Newsgroups | gmane.comp.db.oracle.toad.free |
|---|---|
| Message-ID | <228D4BD15697E04CAF6CD482362F2ACE10301ECB@ALVMBXW01.prod.quest.corp> |
That would be one way - and some time ago I wrote a blog on toad world giving an example of such. Another way would be to maybe use the toad group policy manager - which might support this as well. From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Sent: Monday, January 16, 2012 7:00 AM To: [email protected] Subject: [toad] Preventing access to DB by Toad version Hi, I would like to be able to control which versions of Toad can connect to a given database. We have a situation where developers can take a long time before they upgrade the version of Toad they are using to the newest version regardless of being reminding that they should upgrade. It seems that the carrot of new features isn't enough so I would like to be able to implement the stick of not allowing them access from older versions. What does the list think? Would an on-logon database trigger be the best way to implement this? Thanks, Jonathan