C# - Need to find instances of SQL Server on client
Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance
How can I determine using C# which instances of SQL Server 2000,
MSDE, 2005 or 2005 Express, if any, are installed on a client
computer?
For instance, by knowing the computer's name, I could
guess at a named instance of the data provider and use
it in a connection string, assuming Windows Integrated
Security, and attempt a connection. But this is klutzy.
Is there a method of *discovery* that returns the info?
In Visual Studio 2003/2005 when attempting a new connection
in Server Explorer, an applet appears which does something
like this. Ditto in SQL Server Manager.
The intent is to use DDL, embedded in ADO.Net library
calls, to create a data schema for an application
with stored procedures. This part is easy. But first,
I need to know "who's" there.
.
Relevant Pages
- Re: Connection Error: ADO.Net and SQL Server 2005
... Hitchhiker's Guide to Visual Studio and SQL Server ... I can connect to the server through an ODBC connection ... It is very puzzling because this client doesn't seem to have anything ...
(microsoft.public.sqlserver.connect) - RE: Error 17835 - When encryption and Shared Memory are enabled
... Did you encounter this error when you connected to your SQL Server ... Did your SQL Server instance use a certificate explicitly specified by ... you configure your client connection settings "Force Protocol Encryption" ...
(microsoft.public.sqlserver.connect) - Re: Losing connections with SQL 2005
... Hitchhiker's Guide to Visual Studio and SQL Server ... SQL Server automatically detects if the client falls into the sea or gets ... Does the Connection pooling mechanism do this on its ... Upgrading our app is a really big task, ...
(microsoft.public.sqlserver.connect) - Re: netbios and named pipes sql replication.
... Once the client switched to named pipes, ... > connection with. ... > When we took named pipes support off the SQL server with the MS patch, ... > We had to manually walk thru the ODBC setup and configure the CLIENT ...
(microsoft.public.sqlserver.replication) - Re: Problem connection to SQL Server with ODBC
... What protocols are being used by the client and what is the ... Are you using an alias for the connection? ... SQL Server Clients May Change Protocols When They Try ...
(microsoft.public.sqlserver.connect) |
|
