November 22, 2004 at 3:48 am
In our organisation we have a lot of Access geeks and they connect with odbc to our SQL-servers. In stead of using the applications that where developped for them.
Is there a way to block those ODBC requests on SQL-server? We get a lot of performance issues because they are linking tables with MS Access.
Regards
November 22, 2004 at 5:23 am
take away SELECT from the tables and views. Force everyone to use stored-procedures that are installable by the DBA team only. This will ferret out all of the rogue databases. Had to do this at a prior company at MS insistence. The server performance went up, app time went down, overall everyone was happy when the conversion was complete. Took 60 days to convert our applications (that we remembered).
Good Hunting!
AJ Ahrens
webmaster@kritter.net
November 23, 2004 at 1:31 am
Ok, I'll keep this as an option, we hoped for a more siplistic solution:-)
Thanks anyway...
November 23, 2004 at 8:57 am
A few ideas that may work.
What type of sql autentication is the application that you want the users to use doing?
For example, if the users are connecting with SQL authentication through the ODBC connections, and Windows authentication through the written app, then remove their sql logons.
Or, change the written apps authentication to the opposite of it's current authentication, add the users using the new scheme, and remove them from the other authentication.
Using SQL Enterprise manager, you can determine if the ODBC connetions are using named pipes or TCP/IP to connect. I suspect that the majority are using named pipes; turn off named pipes as a protocol at the server.
Good Luck
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply