MS SQL Server plug in fails with default instance

KByington · Post by **KByington** » Thu Apr 23, 2009 12:43 pm

We have an installer that creates a database using a script and the MS SQL Server plugin. The plug in does not connect to the DB when we attempt to run it against a SQL Server default instance.

The plug in works when we run against a SQL Server named instance. For the default instance, we are leaving the Instance edit box blank in the configuration dialog.

How can we get the MS SQL Server plug in to work against a default instance?

Bar_BQ · Post by **Bar_BQ** » Thu Apr 30, 2009 7:42 am

If blank field doesn't work why don't you try to type "SQLEXPRESS" which is default instance name?

bokkie · Post by **bokkie** » Thu Apr 30, 2009 7:54 am

Bar_BQ wrote:If blank field doesn't work why don't you try to type "SQLEXPRESS" which is default instance name?

Bar_BQ, that's valid unless you have multiple default instances of other versions of SQL Server. I have three versions on my machine and the default instances are all different!

It drive me nuts trying to work out what my apps are pointing to.

Bar_BQ · Post by **Bar_BQ** » Thu Apr 30, 2009 9:25 am

I found this : http://www.sqlnewsgroups.net/group/micr ... 15810.aspx

maybe is worth to try?

bokkie · Post by **bokkie** » Thu Apr 30, 2009 9:31 am

Yup! I endorse the words of wisdom it counsels. I've shafted my installations of SQL Server with indiscriminate registry edits. Fun perhaps, but it reminds me of Yosemite Sam shooting bullets in the air and into the ground.

Bar_BQ · Post by **Bar_BQ** » Tue May 05, 2009 3:49 am

Nice to know that works