question (which uses
named instance) does it work with that?
Bob Beauchemin
http://staff.develop.com/bobb
-Original Message-
From: Martin Welch [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 31, 2002 3:46 AM
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] SqlConnection and na
e-
> From: Beauchemin, Bob [mailto:[EMAIL PROTECTED]]
> Sent: 18 December 2002 17:08
> To: [EMAIL PROTECTED]
> Subject: Re: [ADVANCED-DOTNET] SqlConnection and
> named SQL Server 2000
> instance
>
>
> Named instances work OK here.
>
> A way around using named inst
rom: Beauchemin, Bob [mailto:[EMAIL PROTECTED]]
Sent: 18 December 2002 17:08
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] SqlConnection and named SQL Server 2000
instance
Named instances work OK here.
A way around using named instances at all (something to try if you are
having trouble with them
Named instances work OK here.
A way around using named instances at all (something to try if you are having trouble
with them or using an old API that can't deal with them) is to add an alias in SQL
Server Client configuration utility. Alias a TCP/IP connection to data
source=hoth\\projectx to
PROTECTED]
Subject: Re: [ADVANCED-DOTNET] SqlConnection and named SQL Server 2000
instance
I have used the following format successfully (watch for word wrap -
should
all be on one line):
"initial catalog=MyDbName;data
source=MyServerName\MyNamedInstance;uid=MyUid;pwd=Mypassword;"
My ex
Isn't Hoth a bit cold for Yoda ;)
Seriously, I have a production ASP.Net web application that connects to a named SQL
server instance to authenticate web
users - thousands of times a day.
Can you log in with the credentials in VS.Net, with the connection string builder
dialog for a SqlConnection
Change your Connection String to Look like:
Server=MACHINENAME\INSTANCENAME;Database=DATABASENAME;UID=DBUSER;PWD=DBP
ASS;Max Pool Size=25;Min Pool Size=5;
-Original Message-
From: Martin Welch [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 4:18 AM
To: [EMAIL PROTECTED]
S
I have used the following format successfully (watch for word wrap - should
all be on one line):
"initial catalog=MyDbName;data
source=MyServerName\MyNamedInstance;uid=MyUid;pwd=Mypassword;"
My example is from VB.NET, so the escaped backslash is not required.
>SqlConnection conn = new SqlConnect
This is working fine for me:
SqlConnection conn = new SqlConnection("integrated security=sspi;initial
catalog=pubs;data source=SKYROCKET\\NetSDK;");
conn.Open();
MessageBox.Show(conn.ServerVersion);
So, perhsps the errors are actually correct in your case? Is the server
started? Can yo connect t
OTNET] SqlConnection and named SQL Server 2000
instance
I connect to MSDE databases named .\VSdotnet2003 and .\netsdk all the
time. That may not be much help to you...
> -Original Message-
> From: Martin Welch [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 18, 2002 4:18 AM
> To:
Iain Smallwood [mailto:[EMAIL PROTECTED]]
Sent: 18 December 2002 12:10
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] SqlConnection and named SQL Server 2000
instance
You want to use a single backslash for the datasource i.e. data
source=hoth\projectx.
Tested in that a double one does n
I connect to MSDE databases named .\VSdotnet2003 and .\netsdk all the
time. That may not be much help to you...
> -Original Message-
> From: Martin Welch [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 18, 2002 4:18 AM
> To: [EMAIL PROTECTED]
> Subject: [ADVANCED-DOTNET] SqlConnect
You want to use a single backslash for the datasource i.e. data
source=hoth\projectx.
Tested in that a double one does not work while a single one does (for
me at least!)
Cheers,
Iain
> -Original Message-
> From: Martin Welch [mailto:[EMAIL PROTECTED]]
> Sent: 18 December 2002 09:18
> T
13 matches
Mail list logo
