SQL Server Developer Center >
SQL Server Forums
>
SQL Server Data Access
>
How do you manage ODBC connections across your enterprise?
How do you manage ODBC connections across your enterprise?
Wondering what the best way to manage ODBC system connections across an enterprise. We currently have about 200machines, about 150 of them are production workstations and servers which we would like to distribute certain ODBC connections to. We could put the creation of them in some logon scripts for the machines, but that means you can't push out changes easily. I heard that their may be support for ODBC connections in group policy, but only if you are running Server 2008?
Answers
- The best way to make a "hot swap SQL Server" solution using ODBC is to use file DSNs and put them on a well-known share that is access controlled. Each workstation uses the remote file DSN on the share, and when the server is moved or the configuration is changed, just update the file DSN and the application will then pick up the changes and use the new server location next time it tries to connect.
ODBC is not so much "old fashioned" as it is "tried and true". ADO is out of support, and ADO.NET requires a whole language change of the application. Much like the horse and buggy is old fashioned, but the wheel isn't -- procedural programming is old fashioned, but C/C++/ODBC aren't.
Hope that helps,
John
This post is provided 'as is' and confers no express or implied warranties or rights.- Marked As Answer byJohn C GordonMSFT, ModeratorFriday, November 06, 2009 7:25 PM
All Replies
- Hello bpeikes,
your are using ODBC connections? Isn't it a little bit old-fashioned?
How do you connect to Sql Server / which components do you use (ADO, ADO.NET,...)?
Which security mode do you use; Windows account or a Sql account you devining in UDL?
Surely, it's a problem to create a "hot swap Sql Server" solution, but with ODBC you won't find a good one.
One way is to define a DNS alias for the Sql Server maschine and the apps connect to the alias + instance name. A DNS Alias can be managed centralized.
Olaf Helper ----------- * cogito ergo sum * errare humanum est * quote erat demonstrandum * Wenn ich denke, ist das ein Fehler und das beweise ich täglich http://olafhelper.over-blog.de - The best way to make a "hot swap SQL Server" solution using ODBC is to use file DSNs and put them on a well-known share that is access controlled. Each workstation uses the remote file DSN on the share, and when the server is moved or the configuration is changed, just update the file DSN and the application will then pick up the changes and use the new server location next time it tries to connect.
ODBC is not so much "old fashioned" as it is "tried and true". ADO is out of support, and ADO.NET requires a whole language change of the application. Much like the horse and buggy is old fashioned, but the wheel isn't -- procedural programming is old fashioned, but C/C++/ODBC aren't.
Hope that helps,
John
This post is provided 'as is' and confers no express or implied warranties or rights.- Marked As Answer byJohn C GordonMSFT, ModeratorFriday, November 06, 2009 7:25 PM
