Problems with the VS2005 IDE

I have installed VS2005 MSDN-final, SQL2005, SQL2005 EXPRESS

The problems I have are two

1. I can't add a new sql Database to my windows project due to an error about not being able to start a user instance

2. After I create a new database in SQLExpress, then the datasources window doesnot show the datasource I have created when if form designer view
Any suggestions please

SQLExpress instances must be referenced using its named instance localhost\SQLEXPRESS. If you are doing that then your ok.

Also, make sure the sql services are started.

The datasources window probably only shows you database information that you have configured it for. You would most like have to create a new datasource to see the other database. The datasources is not like the Server Explorer in VS.NET 2003

-HTH|||What I meant Is that the datasources window is disabled when IDE loads the form view designer

Problems when connect sql2005 locally

Hi All,

When I use asp.net 1.1 to connect sql 2005 enterprise server which just enable local access option instead of remote, I got error message to say database server is not avaiable. I use following connection string

user id=abc;password=abc;server=(local);Integrated Security = SSIP;

user id=abc;password=abc;server=.;Integrated Security = SSIP;

Actually, I used default instance, and ASP.Net and database server are in same server. Everything is fine when I change connection string as

user id=abc;password=abc;server=servername;Integrated Security = SSIP;

Frank,

This is a known issue when SS25 does not have TCP on, the client is using MDAC/Everret(.Net1.1) OLEDB provider. For connection sting like (local) or “.”, the connection will fail.

One of the workaround, if TCP/IP is off, is to use hostname in connection string that will connect you through named pipe provider, which is what you have seen.

Thanks,

|||

One more note is that if you can't change the your applications and they use "(local)" and "." in connection string, you can create aliases for "(local)", and "." using tools like cliconfg.exe or SQL Server Configuration Manager.

Please also not that the the there is a typo in your connection string, it should be "SSPI" instead of "SSIP".