Default Versus Named Instance

Default uses: Servername
Named uses: Servername\Instancename
Clusters are a whole different beast entirely. Are you on a cluster or
stand-alone?
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Matt Tinney" <matt.tinney@.css-security.com> wrote in message
news:eeAQaxv$GHA.4292@.TK2MSFTNGP02.phx.gbl...
> When makes an application require the use of a default SQL instance versus
> named instances? If named instances are allowed with an application, how
> does one specify the specific instance to use?
>
> Clusters are a whole different beast entirely. Are you on a cluster or
> stand-alone?
We are talking about connecting to a SQL server instance from a client app;
it should not matter whether or not the SQL instance runs in a cluster.
Linchi
"Kevin3NF" wrote:

> Default uses: Servername
> Named uses: Servername\Instancename
> Clusters are a whole different beast entirely. Are you on a cluster or
> stand-alone?
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> http://kevin3nf.blogspot.com
>
> "Matt Tinney" <matt.tinney@.css-security.com> wrote in message
> news:eeAQaxv$GHA.4292@.TK2MSFTNGP02.phx.gbl...
>
>
|||Except for the Virtual Server name being a required part of the connection
parameters
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:F6590417-338D-4794-B22D-768F497B7857@.microsoft.com...[vbcol=seagreen]
> We are talking about connecting to a SQL server instance from a client
> app;
> it should not matter whether or not the SQL instance runs in a cluster.
> Linchi
> "Kevin3NF" wrote: