Hi,
I'm using the "Detect SQL Server instances" plug-in on a machine having two local instances of SQL Server Express, and the plug-in returns just "(local)". How is this plug-in is supposed to work? Borth instances are Ok, I have databases on both of them.
Is the source code of these plug-ins available somewhere? Or the guidelines to build one yourself?
Regards,
Octavio
SQL Server instances
-
tie_gerben
- Posts: 5
- Joined: Tue Sep 02, 2008 2:42 am
See sample \"SQL Server Connection\"
I have used it succesfully. Well, i have the following in my installer:
Detect MS SQL Instances : get result into variable AVAILABLESERVERS
This returns a list of all servers on the network (with $newline$ between each)
In the sql sample "SQL Server Connection" it is shown how they can be shown in a dropdown box.
btw, i don't have (local) in the list,..., only all servers in our network on which a sql-server is detected. If there are more instances, the server is referred to as
servername\\instancename
Have only seen this for servername's having more than 1 instance.
The ones having only 1 instance don't have the instancename included.
Ah , before I forget. In the sample they say that if no instancename is available, SQLEXPRESS is to be used. This off course only works if the only instance really is SQLEXPRESS. The "Microsoft SQL Server Script" works just fine with an empty instance-name: it will just connect to the one-and-only instance.
Detect MS SQL Instances : get result into variable AVAILABLESERVERS
This returns a list of all servers on the network (with $newline$ between each)
In the sql sample "SQL Server Connection" it is shown how they can be shown in a dropdown box.
btw, i don't have (local) in the list,..., only all servers in our network on which a sql-server is detected. If there are more instances, the server is referred to as
servername\\instancename
Have only seen this for servername's having more than 1 instance.
The ones having only 1 instance don't have the instancename included.
Ah , before I forget. In the sample they say that if no instancename is available, SQLEXPRESS is to be used. This off course only works if the only instance really is SQLEXPRESS. The "Microsoft SQL Server Script" works just fine with an empty instance-name: it will just connect to the one-and-only instance.
Tie gerben,
Thanks for the answer. I attach an image of the "SQL Connections" sample so you see what I mean. In my local machine I have three instances:
a) a SQL Server 2008 Developer Edition (MSSQLSERVER)
b) a SQL Server 2005 Express default instance (MSSQL$SQLEXPRESS)
c) another SQL Server 2005 Express instance (MSSQL$MYCOMPANY)
All three instances are running perfectly.
IA gives me a list with two servers: OCTAVIO-PC (that's the name of my machine) and (local).
Maybe it's because of the 2008?
Regards - Octavio
File Attached:
Servers.jpg
Thanks for the answer. I attach an image of the "SQL Connections" sample so you see what I mean. In my local machine I have three instances:
a) a SQL Server 2008 Developer Edition (MSSQLSERVER)
b) a SQL Server 2005 Express default instance (MSSQL$SQLEXPRESS)
c) another SQL Server 2005 Express instance (MSSQL$MYCOMPANY)
All three instances are running perfectly.
IA gives me a list with two servers: OCTAVIO-PC (that's the name of my machine) and (local).
Maybe it's because of the 2008?
Regards - Octavio
File Attached:
Servers.jpg