Finding BINN directory for Multiple Instances

I am writing an installer that needs to put a dll file with a bunch of
extended stored procedures in the BINN directory. The problem is that
if the machine is running multiple instances of SQL Server, there is
more than one BINN directory. The installer has a dynamically
populated dropdown with the name of the instances, so does anyone know
if this logic is correct and/or reliable assuming SQL Server 2000?

If the instance name = "MSSQLSERVER"
then path to BINN directory = registry value of
HLM\SOFTWARE\Microsoft\MSSQLServer\Setup\SQLPath + "\BINN"

If the instance name != "MSSQLSERVER"
then path to BINN directory = registry value of HLM\SOFTWARE\Microsoft
SQL Server\<Instance Name>\Setup\SQLPath + "\BINN"

Thanks in advance for any help."Bruce" <sandell@.pacbell.net> wrote in message
news:595024a5.0407231210.28d2403c@.posting.google.c om...
> I am writing an installer that needs to put a dll file with a bunch of
> extended stored procedures in the BINN directory. The problem is that
> if the machine is running multiple instances of SQL Server, there is
> more than one BINN directory. The installer has a dynamically
> populated dropdown with the name of the instances, so does anyone know
> if this logic is correct and/or reliable assuming SQL Server 2000?
> If the instance name = "MSSQLSERVER"
> then path to BINN directory = registry value of
> HLM\SOFTWARE\Microsoft\MSSQLServer\Setup\SQLPath + "\BINN"
> If the instance name != "MSSQLSERVER"
> then path to BINN directory = registry value of HLM\SOFTWARE\Microsoft
> SQL Server\<Instance Name>\Setup\SQLPath + "\BINN"
> Thanks in advance for any help.

See questions 12 and 13:

http://support.microsoft.com/defaul...6&Product=sql2k

Simon

Find SQL Servers 2000 & 2005 on the net

In order to find SQL Servers 2000, in my .NET application, I successfully use
"SQLBrowseConnect" from ODBC32.DLL. But this doesn't seem to find instances
of SQL Servers 2005.
Is there anything else available to do this job? Thanks for any hint.
Axel Hecker
To see SQL 2005 instances using enumeration APIs, the SQL Browser service
needs to be running on each SQL 2005 server and the instance not explicitly
hidden.
Hope this helps.
Dan Guzman
SQL Server MVP
"AxelHecker" <AxelHecker@.discussions.microsoft.com> wrote in message
news:73AB9D63-3B29-4926-A2F8-0330DDFF5D11@.microsoft.com...
> In order to find SQL Servers 2000, in my .NET application, I successfully
> use
> "SQLBrowseConnect" from ODBC32.DLL. But this doesn't seem to find
> instances
> of SQL Servers 2005.
> Is there anything else available to do this job? Thanks for any hint.
> Axel Hecker
>
|||Thanks for your reply!
SQL Browser service is running, and the instance is not hidden. But I think
I found out what was wrong: I assumed that SQLBrowseConnect would also find
local instances (which is not true).
Thanks anyway,
Axel Hecker
"Dan Guzman" schrieb:

> To see SQL 2005 instances using enumeration APIs, the SQL Browser service
> needs to be running on each SQL 2005 server and the instance not explicitly
> hidden.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "AxelHecker" <AxelHecker@.discussions.microsoft.com> wrote in message
> news:73AB9D63-3B29-4926-A2F8-0330DDFF5D11@.microsoft.com...
>
>

Find SQL Servers 2000 & 2005 on the net

In order to find SQL Servers 2000, in my .NET application, I successfully use
"SQLBrowseConnect" from ODBC32.DLL. But this doesn't seem to find instances
of SQL Servers 2005.
Is there anything else available to do this job? Thanks for any hint.
Axel HeckerTo see SQL 2005 instances using enumeration APIs, the SQL Browser service
needs to be running on each SQL 2005 server and the instance not explicitly
hidden.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"AxelHecker" <AxelHecker@.discussions.microsoft.com> wrote in message
news:73AB9D63-3B29-4926-A2F8-0330DDFF5D11@.microsoft.com...
> In order to find SQL Servers 2000, in my .NET application, I successfully
> use
> "SQLBrowseConnect" from ODBC32.DLL. But this doesn't seem to find
> instances
> of SQL Servers 2005.
> Is there anything else available to do this job? Thanks for any hint.
> Axel Hecker
>|||Thanks for your reply!
SQL Browser service is running, and the instance is not hidden. But I think
I found out what was wrong: I assumed that SQLBrowseConnect would also find
local instances (which is not true).
Thanks anyway,
Axel Hecker
"Dan Guzman" schrieb:
> To see SQL 2005 instances using enumeration APIs, the SQL Browser service
> needs to be running on each SQL 2005 server and the instance not explicitly
> hidden.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "AxelHecker" <AxelHecker@.discussions.microsoft.com> wrote in message
> news:73AB9D63-3B29-4926-A2F8-0330DDFF5D11@.microsoft.com...
> > In order to find SQL Servers 2000, in my .NET application, I successfully
> > use
> > "SQLBrowseConnect" from ODBC32.DLL. But this doesn't seem to find
> > instances
> > of SQL Servers 2005.
> >
> > Is there anything else available to do this job? Thanks for any hint.
> >
> > Axel Hecker
> >
>
>

Find SQL Servers 2000 & 2005 on the net

In order to find SQL Servers 2000, in my .NET application, I successfully us
e
"SQLBrowseConnect" from ODBC32.DLL. But this doesn't seem to find instances
of SQL Servers 2005.
Is there anything else available to do this job? Thanks for any hint.
Axel HeckerTo see SQL 2005 instances using enumeration APIs, the SQL Browser service
needs to be running on each SQL 2005 server and the instance not explicitly
hidden.
Hope this helps.
Dan Guzman
SQL Server MVP
"AxelHecker" <AxelHecker@.discussions.microsoft.com> wrote in message
news:73AB9D63-3B29-4926-A2F8-0330DDFF5D11@.microsoft.com...
> In order to find SQL Servers 2000, in my .NET application, I successfully
> use
> "SQLBrowseConnect" from ODBC32.DLL. But this doesn't seem to find
> instances
> of SQL Servers 2005.
> Is there anything else available to do this job? Thanks for any hint.
> Axel Hecker
>|||Thanks for your reply!
SQL Browser service is running, and the instance is not hidden. But I think
I found out what was wrong: I assumed that SQLBrowseConnect would also find
local instances (which is not true).
Thanks anyway,
Axel Hecker
"Dan Guzman" schrieb:

> To see SQL 2005 instances using enumeration APIs, the SQL Browser service
> needs to be running on each SQL 2005 server and the instance not explicitl
y
> hidden.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "AxelHecker" <AxelHecker@.discussions.microsoft.com> wrote in message
> news:73AB9D63-3B29-4926-A2F8-0330DDFF5D11@.microsoft.com...
>
>