RAM (r_********@poczta.onet.pl) writes:
I have noticed something interesting.
The problem occurs when I am configuring data source control. The
connection string is taken from web.config:
<add name="MIMMagazynDemo" connectionString="Data Source=localhost;Initial
Catalog=MIMMagazynDemo;Integrated Security=True"
providerName="System.Data.SqlClient" />
I have noticed that the problem do not exist when I change localhost to
PC\SQLEXPRESS (PC is name of my computer).
Could you explain me why? Thank you!
SQL Server permits you to install several instances on the same machine.
One of these instances can be a default instances, all other instances
must be named.
When you refer to a default instance, you refer only to the machine name,
or, if you are on the machine itself, you can use ".", "localhost" or
"(local)" instead.
When you refer to a named instance, you must also include the instance
name separated from the machine name with a backslash, for instance
MYSERVER\MY2NDINSTANCE.
By default, SQL Server Express is installed as a named instance as
SQLEXPRESS, and thus "localhost" alone will not work on a machine that
only has SQL Express.
--
Erland Sommarskog, SQL Server MVP,
es****@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx