Connectionstring

Im using sql server express advanced edition and Windows Vista. My Windows
account doesnt have any permissions to the sql server at all, so I need to
use sql server logins in my connectionstring. How can I provide that when
using attachdb?
This is my connectionstring today:
Data Source=. \SQLEXPRESS;AttachDbFilename=|DataDirect
ory|\site_db.mdf;User
Instance=False;Initial Catalog=site_db;
StigSee http://www.microsoft.com/sql/howtob...stasupport.mspx for
considerations on using SQL 2005 under Vista. Note that SP2 is still in CTP
(beta).
I haven't played around with SQL Express but you ought to be able to add the
desired SQL login credentials in the connection string:
Data Source=. \SQLEXPRESS;AttachDbFilename=|DataDirect
ory|\site_db.mdf;User
Instance=False;Initial Catalog=site_db;User Id=MyLogin;Password=MyPassword
Hope this helps.
Dan Guzman
SQL Server MVP
"Stig Kulvedrsten" <stig@.spire.as> wrote in message
news:0ABA74C2-E6C4-4E84-B331-3633D0BEC597@.microsoft.com...
> Im using sql server express advanced edition and Windows Vista. My Windows
> account doesnt have any permissions to the sql server at all, so I need to
> use sql server logins in my connectionstring. How can I provide that when
> using attachdb?
> This is my connectionstring today:
> Stig|||I reinstalled and got my sql server express up and running. I then loaded up
VS.NET and tried to run my website.
Right away I got this error:
Timeout expired. The timeout period elapsed prior to obtaining a connection
from the pool. This may have occurred because all pooled connections were
in use and max pool size was reached.
What causes this error at first runtime?
Stig
"Stig Kulvedrsten" <stig@.spire.as> wrote in message
news:0ABA74C2-E6C4-4E84-B331-3633D0BEC597@.microsoft.com...
> Im using sql server express advanced edition and Windows Vista. My Windows
> account doesnt have any permissions to the sql server at all, so I need to
> use sql server logins in my connectionstring. How can I provide that when
> using attachdb?
> This is my connectionstring today:
> Data Source=. \SQLEXPRESS;AttachDbFilename=|DataDirect
ory|\site_db.mdf;User
> Instance=False;Initial Catalog=site_db;
> Stig

Connection problem from Vista

I can't connect from a Vista Client to a SQL 2005 Server.
I have been stuck on this problem over a week so any help would be greatly appreciated.

Overview:
I cannot connect from my client (vista business) except with SQL Server Management Studio.
I have tried Red Gate SQL Compare connection from a machine running XP and it connects ok.
I have tried connecting using ODBC from another machine running Vista Home and it connects ok.
I have no problem connecting to my local SQL Server (on my client).
I have tried using Windows Auth and a SQL login.

Environment:
Both the client and server are on the same domain and the user is a domain user.

Client:
Vista Business, SQL Server 2005 SP1 Client tools and Server, RedGate tools, Visual Studio 2005 SP1
Windows Firewall OFF

Norton virus protection OFF

UAC is turned OFF

Server:
SQL Server 2005 SP1, Remote connections allowed over TCP/IP Port 1433 (IPAll TCP Port 1433, not dynamic)
No windows firewall, Mcaffee virus running.

I get the errors below (or similar) connecting from:
SQL Profiler
Database engine tuning advisor,
Redgate SQL Compare (or any redgate software)
Setting up an ODBC connection
Visual Studio 2005 SP1

The only application that current connects is SQL Server Management Studio!?
If I apply SQL Server 2005 SP2 to the client it stops even SQL Server Management Studio from working.

I either get the following error:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error:0 - No process is on the other end of the pipe.)

or (if I force the port and/or method e.g. TCP:192.168.130.3,1433)

A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
(provider: TCP Provider, error:0 - No connection could be made because the target machine actively refused it.)

Again any help would be much appreciated as I just can not seem to solve this.

Thanks

Please check out following blog:

http://blogs.msdn.com/sql_protocols/archive/2007/06/18/connecting-to-sql-server-2005-on-vista-and-longhorn.aspx

Good Luck!

Ming.

Connection problem from Vista

I can't connect from a Vista Client to a SQL 2005 Server.
I have been stuck on this problem over a week so any help would be greatly appreciated.

Overview:
I cannot connect from my client (vista business) except with SQL Server Management Studio.
I have tried Red Gate SQL Compare connection from a machine running XP and it connects ok.
I have tried connecting using ODBC from another machine running Vista Home and it connects ok.
I have no problem connecting to my local SQL Server (on my client).
I have tried using Windows Auth and a SQL login.

Environment:
Both the client and server are on the same domain and the user is a domain user.

Client:
Vista Business, SQL Server 2005 SP1 Client tools and Server, RedGate tools, Visual Studio 2005 SP1
Windows Firewall OFF

Norton virus protection OFF

UAC is turned OFF

Server:
SQL Server 2005 SP1, Remote connections allowed over TCP/IP Port 1433 (IPAll TCP Port 1433, not dynamic)
No windows firewall, Mcaffee virus running.

I get the errors below (or similar) connecting from:
SQL Profiler
Database engine tuning advisor,
Redgate SQL Compare (or any redgate software)
Setting up an ODBC connection
Visual Studio 2005 SP1

The only application that current connects is SQL Server Management Studio!?
If I apply SQL Server 2005 SP2 to the client it stops even SQL Server Management Studio from working.

I either get the following error:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error:0 - No process is on the other end of the pipe.)

or (if I force the port and/or method e.g. TCP:192.168.130.3,1433)

A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
(provider: TCP Provider, error:0 - No connection could be made because the target machine actively refused it.)

Again any help would be much appreciated as I just can not seem to solve this.

Thanks

Please check out following blog:

http://blogs.msdn.com/sql_protocols/archive/2007/06/18/connecting-to-sql-server-2005-on-vista-and-longhorn.aspx

Good Luck!

Ming.