vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, I'd like to prevent Excel and Access (well any Microsoft Office application) from gaining access to a SQL 2000 instance, via an ODBC connection. If this we're SQL 2005, I create a logon trigger, and just kill off unwanted connections. Can anyone suggest how I can achieve this is SQL 2000? Thanks, James. |
| |||
| Jimbo (james.goodwill@googlemail.com) writes: > I'd like to prevent Excel and Access (well any Microsoft Office > application) from gaining access to a SQL 2000 instance, via an > ODBC connection. > > If this we're SQL 2005, I create a logon trigger, and just kill off > unwanted connections. > > Can anyone suggest how I can achieve this is SQL 2000? A scheduled job that runs once a minute, and which looks at the program_name column in sysprocesses and kills it off if the name is unsuitable. Users that knows how to write a connection string, can work around that though. (Then again, they can work around your login trigger on SQL 2005 as well.) -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/pro...ads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinf...ons/books.mspx |
| ||||
| "Jimbo" <james.goodwill@googlemail.com> skrev i en meddelelse news:6ef5740f-32cb-40ad-8239-92783057072d@d45g2000hsc.googlegroups.com... > Hi, > > I'd like to prevent Excel and Access (well any Microsoft Office > application) from gaining access to a SQL 2000 instance, via an > ODBC connection. > Ever heard of passwords? |