Do you need to determine connection information for one or more
instances of SQL Server (versions 2005, 2000, 7.0) on your local
machine? (be it a server or a PC)
Here is a simple solution to a problem that is a royal pain in
kiester to deal with. Sure, if you are a DBA making an ODBC or a JDBC
connection is not a big deal. Actually it is a pretty routine affair.
But to every one else that is trying to maintain run a local instance of
SQL Server it is not so easy. I can't tell you how many developers,
designers, test engineers, report writers and other professionals we
have supported over the years in this very endeavor.
If you can remember back to the last time you had to make an initial
connection you are probably nodding your head and chuckling. Many of you
did it so long ago you probably forgot where to get this
information...especially the port number. I am sure there are many of
you out that like me wonder why gather a few parameters and making a
connection can be such a traumatic experience?
Those of you that have had bad experiences connecting you can come
out of the closet. I recently Googled the following keywords and as you
can see the number of indexed pages would indicate that it is not just
you and I are the only ones that have had this problem. |
