Connecting to SQL database

I am moving my site from a shared environment to a dedicated server and SQL is on the same box. How do I connect to my database if it's on the same box?in your connection string, reference your data source or server as "." or (local)|||

Thank you. This is my first time setting up a SQL server. Is there a special login account I need to set up for my web pages to use?

|||you can use integrated security... if your running win2003, the account will be [network service], if xp pro, [aspnet]
if you want to use sql server authentication, add a user to your server, make the user a dbo over your database. but this way, you have to put the username and pw into the query string. :)
http://www.connectionstrings.com/ <-- that might help|||

I just uploaded a training video that covers this. :)
http://www.dotnetnukerocks.com/Administering/GettingStarted/Installation/DotNetNukev40InstallVideo/tabid/2574/Default.aspx

Connecting to SQL 2005

I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
connect to the server within the same box. When I try to connect to the 2005
SQL server from an other desktop using SQL Server Management studio, I get a
timeout error. Can you please help me to fix this.
This is waht I get when I connect to the SQL server from another computer...
===================================
Cannot connect to CWXPTDVZPT62.
===================================
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding. (.Net SqlClient Data Provider)
For help, click:
http://go.microsoft.com/fwlink?Prod...-2&LinkId=20476
Server Name: CWXPTDVZPT62
Error Number: -2
Severity: 11
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser. ThrowExceptionAndWarning(TdsParserStateO
bjec
t
stateObj)
at
System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
stateObj, UInt32 error, Boolean freePacket)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
enlistOK)
at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
connectionOptions, Object providerInfo, String newPassword, SqlConnection
owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOpti
ons
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbCon
nection owningConnection, DbConnectionPoolGroup poolGroup)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at
Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplore
r.ValidateConnection(UIConnectionInfo ci, IServerType server)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUs
er()Hi Mahesh,
Starting with the June CTP version, remote access to an instance of SQL
Server 2005 is off by default. You can enable remote access by using the
Surface Area Configuration (SAC) tool.
On the local server:
1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
Configuration Tools | SQL Server Surface Area Configuration
2. From the SAC tool, select Surface Area Configuration for Services and
Connections
3. Under Database Engine, select Remote Connections and then select the
Local and Remote Connections and one of the options under that.
4. Click Apply.
5. You'll need to stop and start the MSSQLSERVER service. You can do that
from the SAC as well. Just click Service under Database Engine and
stop/start the service.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
> connect to the server within the same box. When I try to connect to the
> 2005
> SQL server from an other desktop using SQL Server Management studio, I get
> a
> timeout error. Can you please help me to fix this.
> This is waht I get when I connect to the SQL server from another
> computer...
> ===================================
> Cannot connect to CWXPTDVZPT62.
> ===================================
> Timeout expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding. (.Net SqlClient Data Provider)
> --
> For help, click:
> http://go.microsoft.com/fwlink?Prod...-2&LinkId=20476
> --
> Server Name: CWXPTDVZPT62
> Error Number: -2
> Severity: 11
> State: 0
>
> --
> Program Location:
> at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
> exception, Boolean breakConnection)
> at
> System.Data.SqlClient.TdsParser. ThrowExceptionAndWarning(TdsParserStateO
bj
ect
> stateObj)
> at
> System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObje
ct
> stateObj, UInt32 error, Boolean freePacket)
> at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
> asyncResult, TdsParserStateObject stateObj)
> at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
> bytesExpected)
> at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
> at System.Data.SqlClient.TdsParserStateObject.ReadByte()
> at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
> SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
> bulkCopyHandler, TdsParserStateObject stateObj)
> at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
> enlistOK)
> at
> System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnecti
on
> owningObject, SqlConnectionString connectionOptions, String newPassword,
> Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
> connectionOptions, Object providerInfo, String newPassword, SqlConnection
> owningObject, Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOp
tions
> options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbC
onnection
> owningConnection, DbConnectionPoolGroup poolGroup)
> at
> System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
> outerConnection, DbConnectionFactory connectionFactory)
> at System.Data.SqlClient.SqlConnection.Open()
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplo
rer.ValidateConnection(UIConnectionInfo
> ci, IServerType server)
> at
> Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThread
User()
>|||Gail
Thank you for the answer, I checked the Surface area configuration and set
the option to “Local and Remote connections” and select the option to
use
both TCP/IP and named Pipes”.
I tried again to register the 2005 SQL server from Management studio of
another computer. I was able to register/connect only when I selected the
option “Named Pipes” in Connect properties for Network Protocol. When Ne
twork
Protocol option was set to “default” I got Timeout errors.
Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
Native client, I was able to view the Databases, but when I tested the
connection I got a timeout error.
I can connect to the 2005 server using query analyzer or thro creating an
ODBC.
Please advice.
Thanks again for all your help
Mahesh
"Gail Erickson [MS]" wrote:

> Hi Mahesh,
> Starting with the June CTP version, remote access to an instance of SQL
> Server 2005 is off by default. You can enable remote access by using the
> Surface Area Configuration (SAC) tool.
> On the local server:
> 1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
> Configuration Tools | SQL Server Surface Area Configuration
> 2. From the SAC tool, select Surface Area Configuration for Services and
> Connections
> 3. Under Database Engine, select Remote Connections and then select the
> Local and Remote Connections and one of the options under that.
> 4. Click Apply.
> 5. You'll need to stop and start the MSSQLSERVER service. You can do tha
t
> from the SAC as well. Just click Service under Database Engine and
> stop/start the service.
> --
> Gail Erickson [MS]
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
> news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>
>|||Hi Mahesh,
Your follow-up questions are a bit out of area of experience. Please post
your questions to the Setup and DTS newsgroups at this link:
http://communities.microsoft.com/ne...p=sqlserver2005
They should be able to give you some advice.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:8DC49354-F7FC-4979-94A9-3DB20CF6B71E@.microsoft.com...[vbcol=seagreen]
> Gail
> Thank you for the answer, I checked the Surface area configuration and set
> the option to "Local and Remote connections" and select the option to "use
> both TCP/IP and named Pipes".
> I tried again to register the 2005 SQL server from Management studio of
> another computer. I was able to register/connect only when I selected the
> option "Named Pipes" in Connect properties for Network Protocol. When
> Network
> Protocol option was set to "default" I got Timeout errors.
> Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
> Native client, I was able to view the Databases, but when I tested the
> connection I got a timeout error.
> I can connect to the 2005 server using query analyzer or thro creating an
> ODBC.
> Please advice.
> Thanks again for all your help
> Mahesh
> "Gail Erickson [MS]" wrote:
>

Connecting to SQL 2005

I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
connect to the server within the same box. When I try to connect to the 2005
SQL server from an other desktop using SQL Server Management studio, I get a
timeout error. Can you please help me to fix this.
This is waht I get when I connect to the SQL server from another computer...
===================================
Cannot connect to CWXPTDVZPT62.
===================================
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding. (.Net SqlClient Data Provider)
For help, click:
http://go.microsoft.com/fwlink?ProdN...2&LinkId=20476
Server Name: CWXPTDVZPT62
Error Number: -2
Severity: 11
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
stateObj)
at
System.Data.SqlClient.TdsParserStateObject.ReadSni Error(TdsParserStateObject
stateObj, UInt32 error, Boolean freePacket)
at System.Data.SqlClient.TdsParserStateObject.ReadSni (DbAsyncResult
asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPac ket(Int32
bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuf fer()
at System.Data.SqlClient.TdsParserStateObject.ReadByt e()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.Com pleteLogin(Boolean
enlistOK)
at
System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ct or(SqlConnectionString
connectionOptions, Object providerInfo, String newPassword, SqlConnection
owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.Creat eNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.ObjectExplorer.ValidateConnection(UIC onnectionInfo ci, IServerType server)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Co nnector.ConnectionThreadUser()
Hi Mahesh,
Starting with the June CTP version, remote access to an instance of SQL
Server 2005 is off by default. You can enable remote access by using the
Surface Area Configuration (SAC) tool.
On the local server:
1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
Configuration Tools | SQL Server Surface Area Configuration
2. From the SAC tool, select Surface Area Configuration for Services and
Connections
3. Under Database Engine, select Remote Connections and then select the
Local and Remote Connections and one of the options under that.
4. Click Apply.
5. You'll need to stop and start the MSSQLSERVER service. You can do that
from the SAC as well. Just click Service under Database Engine and
stop/start the service.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
> connect to the server within the same box. When I try to connect to the
> 2005
> SQL server from an other desktop using SQL Server Management studio, I get
> a
> timeout error. Can you please help me to fix this.
> This is waht I get when I connect to the SQL server from another
> computer...
> ===================================
> Cannot connect to CWXPTDVZPT62.
> ===================================
> Timeout expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding. (.Net SqlClient Data Provider)
> --
> For help, click:
> http://go.microsoft.com/fwlink?ProdN...2&LinkId=20476
> --
> Server Name: CWXPTDVZPT62
> Error Number: -2
> Severity: 11
> State: 0
>
> --
> Program Location:
> at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
> exception, Boolean breakConnection)
> at
> System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
> stateObj)
> at
> System.Data.SqlClient.TdsParserStateObject.ReadSni Error(TdsParserStateObject
> stateObj, UInt32 error, Boolean freePacket)
> at System.Data.SqlClient.TdsParserStateObject.ReadSni (DbAsyncResult
> asyncResult, TdsParserStateObject stateObj)
> at System.Data.SqlClient.TdsParserStateObject.ReadPac ket(Int32
> bytesExpected)
> at System.Data.SqlClient.TdsParserStateObject.ReadBuf fer()
> at System.Data.SqlClient.TdsParserStateObject.ReadByt e()
> at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
> SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
> bulkCopyHandler, TdsParserStateObject stateObj)
> at System.Data.SqlClient.SqlInternalConnectionTds.Com pleteLogin(Boolean
> enlistOK)
> at
> System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
> owningObject, SqlConnectionString connectionOptions, String newPassword,
> Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlInternalConnectionTds..ct or(SqlConnectionString
> connectionOptions, Object providerInfo, String newPassword, SqlConnection
> owningObject, Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
> options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionFactory.Creat eNonPooledConnection(DbConnection
> owningConnection, DbConnectionPoolGroup poolGroup)
> at
> System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
> outerConnection, DbConnectionFactory connectionFactory)
> at System.Data.SqlClient.SqlConnection.Open()
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.ObjectExplorer.ValidateConnection(UIC onnectionInfo
> ci, IServerType server)
> at
> Microsoft.SqlServer.Management.UI.ConnectionDlg.Co nnector.ConnectionThreadUser()
>
|||Gail
Thank you for the answer, I checked the Surface area configuration and set
the option to “Local and Remote connections” and select the option to “use
both TCP/IP and named Pipes”.
I tried again to register the 2005 SQL server from Management studio of
another computer. I was able to register/connect only when I selected the
option “Named Pipes” in Connect properties for Network Protocol. When Network
Protocol option was set to “default” I got Timeout errors.
Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
Native client, I was able to view the Databases, but when I tested the
connection I got a timeout error.
I can connect to the 2005 server using query analyzer or thro creating an
ODBC.
Please advice.
Thanks again for all your help
Mahesh
"Gail Erickson [MS]" wrote:

> Hi Mahesh,
> Starting with the June CTP version, remote access to an instance of SQL
> Server 2005 is off by default. You can enable remote access by using the
> Surface Area Configuration (SAC) tool.
> On the local server:
> 1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
> Configuration Tools | SQL Server Surface Area Configuration
> 2. From the SAC tool, select Surface Area Configuration for Services and
> Connections
> 3. Under Database Engine, select Remote Connections and then select the
> Local and Remote Connections and one of the options under that.
> 4. Click Apply.
> 5. You'll need to stop and start the MSSQLSERVER service. You can do that
> from the SAC as well. Just click Service under Database Engine and
> stop/start the service.
> --
> Gail Erickson [MS]
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
> news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>
>
|||Hi Mahesh,
Your follow-up questions are a bit out of area of experience. Please post
your questions to the Setup and DTS newsgroups at this link:
http://communities.microsoft.com/new...=sqlserver2005
They should be able to give you some advice.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:8DC49354-F7FC-4979-94A9-3DB20CF6B71E@.microsoft.com...[vbcol=seagreen]
> Gail
> Thank you for the answer, I checked the Surface area configuration and set
> the option to "Local and Remote connections" and select the option to "use
> both TCP/IP and named Pipes".
> I tried again to register the 2005 SQL server from Management studio of
> another computer. I was able to register/connect only when I selected the
> option "Named Pipes" in Connect properties for Network Protocol. When
> Network
> Protocol option was set to "default" I got Timeout errors.
> Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
> Native client, I was able to view the Databases, but when I tested the
> connection I got a timeout error.
> I can connect to the 2005 server using query analyzer or thro creating an
> ODBC.
> Please advice.
> Thanks again for all your help
> Mahesh
> "Gail Erickson [MS]" wrote:

Connecting to SQL 2005

I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
connect to the server within the same box. When I try to connect to the 2005
SQL server from an other desktop using SQL Server Management studio, I get a
timeout error. Can you please help me to fix this.
This is waht I get when I connect to the SQL server from another computer...
===================================
Cannot connect to CWXPTDVZPT62.
===================================
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding. (.Net SqlClient Data Provider)
--
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
--
Server Name: CWXPTDVZPT62
Error Number: -2
Severity: 11
State: 0
--
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)
at
System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
stateObj, UInt32 error, Boolean freePacket)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
enlistOK)
at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
connectionOptions, Object providerInfo, String newPassword, SqlConnection
owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at
Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()Hi Mahesh,
Starting with the June CTP version, remote access to an instance of SQL
Server 2005 is off by default. You can enable remote access by using the
Surface Area Configuration (SAC) tool.
On the local server:
1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
Configuration Tools | SQL Server Surface Area Configuration
2. From the SAC tool, select Surface Area Configuration for Services and
Connections
3. Under Database Engine, select Remote Connections and then select the
Local and Remote Connections and one of the options under that.
4. Click Apply.
5. You'll need to stop and start the MSSQLSERVER service. You can do that
from the SAC as well. Just click Service under Database Engine and
stop/start the service.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
> connect to the server within the same box. When I try to connect to the
> 2005
> SQL server from an other desktop using SQL Server Management studio, I get
> a
> timeout error. Can you please help me to fix this.
> This is waht I get when I connect to the SQL server from another
> computer...
> ===================================> Cannot connect to CWXPTDVZPT62.
> ===================================> Timeout expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding. (.Net SqlClient Data Provider)
> --
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
> --
> Server Name: CWXPTDVZPT62
> Error Number: -2
> Severity: 11
> State: 0
>
> --
> Program Location:
> at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
> exception, Boolean breakConnection)
> at
> System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
> stateObj)
> at
> System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
> stateObj, UInt32 error, Boolean freePacket)
> at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
> asyncResult, TdsParserStateObject stateObj)
> at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
> bytesExpected)
> at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
> at System.Data.SqlClient.TdsParserStateObject.ReadByte()
> at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
> SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
> bulkCopyHandler, TdsParserStateObject stateObj)
> at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
> enlistOK)
> at
> System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
> owningObject, SqlConnectionString connectionOptions, String newPassword,
> Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
> connectionOptions, Object providerInfo, String newPassword, SqlConnection
> owningObject, Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
> options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection
> owningConnection, DbConnectionPoolGroup poolGroup)
> at
> System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
> outerConnection, DbConnectionFactory connectionFactory)
> at System.Data.SqlClient.SqlConnection.Open()
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo
> ci, IServerType server)
> at
> Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
>|||Gail
Thank you for the answer, I checked the Surface area configuration and set
the option to â'Local and Remote connectionsâ' and select the option to â'use
both TCP/IP and named Pipesâ'.
I tried again to register the 2005 SQL server from Management studio of
another computer. I was able to register/connect only when I selected the
option â'Named Pipesâ' in Connect properties for Network Protocol. When Network
Protocol option was set to â'defaultâ' I got Timeout errors.
Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
Native client, I was able to view the Databases, but when I tested the
connection I got a timeout error.
I can connect to the 2005 server using query analyzer or thro creating an
ODBC.
Please advice.
Thanks again for all your help
Mahesh
"Gail Erickson [MS]" wrote:
> Hi Mahesh,
> Starting with the June CTP version, remote access to an instance of SQL
> Server 2005 is off by default. You can enable remote access by using the
> Surface Area Configuration (SAC) tool.
> On the local server:
> 1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
> Configuration Tools | SQL Server Surface Area Configuration
> 2. From the SAC tool, select Surface Area Configuration for Services and
> Connections
> 3. Under Database Engine, select Remote Connections and then select the
> Local and Remote Connections and one of the options under that.
> 4. Click Apply.
> 5. You'll need to stop and start the MSSQLSERVER service. You can do that
> from the SAC as well. Just click Service under Database Engine and
> stop/start the service.
> --
> Gail Erickson [MS]
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
> news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
> >I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
> > connect to the server within the same box. When I try to connect to the
> > 2005
> > SQL server from an other desktop using SQL Server Management studio, I get
> > a
> > timeout error. Can you please help me to fix this.
> >
> > This is waht I get when I connect to the SQL server from another
> > computer...
> > ===================================> >
> > Cannot connect to CWXPTDVZPT62.
> >
> > ===================================> >
> > Timeout expired. The timeout period elapsed prior to completion of the
> > operation or the server is not responding. (.Net SqlClient Data Provider)
> >
> > --
> > For help, click:
> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
> >
> > --
> > Server Name: CWXPTDVZPT62
> > Error Number: -2
> > Severity: 11
> > State: 0
> >
> >
> > --
> > Program Location:
> >
> > at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
> > exception, Boolean breakConnection)
> > at
> > System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
> > stateObj)
> > at
> > System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
> > stateObj, UInt32 error, Boolean freePacket)
> > at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
> > asyncResult, TdsParserStateObject stateObj)
> > at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
> > bytesExpected)
> > at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
> > at System.Data.SqlClient.TdsParserStateObject.ReadByte()
> > at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
> > SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
> > bulkCopyHandler, TdsParserStateObject stateObj)
> > at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
> > enlistOK)
> > at
> > System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
> > owningObject, SqlConnectionString connectionOptions, String newPassword,
> > Boolean redirectedUserInstance)
> > at
> > System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
> > connectionOptions, Object providerInfo, String newPassword, SqlConnection
> > owningObject, Boolean redirectedUserInstance)
> > at
> > System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
> > options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
> > owningConnection)
> > at
> > System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection
> > owningConnection, DbConnectionPoolGroup poolGroup)
> > at
> > System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
> > owningConnection)
> > at
> > System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
> > outerConnection, DbConnectionFactory connectionFactory)
> > at System.Data.SqlClient.SqlConnection.Open()
> > at
> > Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo
> > ci, IServerType server)
> > at
> > Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
> >
> >
>
>|||Hi Mahesh,
Your follow-up questions are a bit out of area of experience. Please post
your questions to the Setup and DTS newsgroups at this link:
http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005
They should be able to give you some advice.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:8DC49354-F7FC-4979-94A9-3DB20CF6B71E@.microsoft.com...
> Gail
> Thank you for the answer, I checked the Surface area configuration and set
> the option to "Local and Remote connections" and select the option to "use
> both TCP/IP and named Pipes".
> I tried again to register the 2005 SQL server from Management studio of
> another computer. I was able to register/connect only when I selected the
> option "Named Pipes" in Connect properties for Network Protocol. When
> Network
> Protocol option was set to "default" I got Timeout errors.
> Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
> Native client, I was able to view the Databases, but when I tested the
> connection I got a timeout error.
> I can connect to the 2005 server using query analyzer or thro creating an
> ODBC.
> Please advice.
> Thanks again for all your help
> Mahesh
> "Gail Erickson [MS]" wrote:
>> Hi Mahesh,
>> Starting with the June CTP version, remote access to an instance of SQL
>> Server 2005 is off by default. You can enable remote access by using the
>> Surface Area Configuration (SAC) tool.
>> On the local server:
>> 1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
>> Configuration Tools | SQL Server Surface Area Configuration
>> 2. From the SAC tool, select Surface Area Configuration for Services and
>> Connections
>> 3. Under Database Engine, select Remote Connections and then select the
>> Local and Remote Connections and one of the options under that.
>> 4. Click Apply.
>> 5. You'll need to stop and start the MSSQLSERVER service. You can do
>> that
>> from the SAC as well. Just click Service under Database Engine and
>> stop/start the service.
>> --
>> Gail Erickson [MS]
>> SQL Server Documentation Team
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights
>> "Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
>> news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>> >I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able
>> >to
>> > connect to the server within the same box. When I try to connect to the
>> > 2005
>> > SQL server from an other desktop using SQL Server Management studio, I
>> > get
>> > a
>> > timeout error. Can you please help me to fix this.
>> >
>> > This is waht I get when I connect to the SQL server from another
>> > computer...
>> > ===================================>> >
>> > Cannot connect to CWXPTDVZPT62.
>> >
>> > ===================================>> >
>> > Timeout expired. The timeout period elapsed prior to completion of the
>> > operation or the server is not responding. (.Net SqlClient Data
>> > Provider)
>> >
>> > --
>> > For help, click:
>> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
>> >
>> > --
>> > Server Name: CWXPTDVZPT62
>> > Error Number: -2
>> > Severity: 11
>> > State: 0
>> >
>> >
>> > --
>> > Program Location:
>> >
>> > at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
>> > exception, Boolean breakConnection)
>> > at
>> > System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
>> > stateObj)
>> > at
>> > System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
>> > stateObj, UInt32 error, Boolean freePacket)
>> > at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
>> > asyncResult, TdsParserStateObject stateObj)
>> > at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
>> > bytesExpected)
>> > at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
>> > at System.Data.SqlClient.TdsParserStateObject.ReadByte()
>> > at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
>> > SqlCommand cmdHandler, SqlDataReader dataStream,
>> > BulkCopySimpleResultSet
>> > bulkCopyHandler, TdsParserStateObject stateObj)
>> > at
>> > System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
>> > enlistOK)
>> > at
>> > System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
>> > owningObject, SqlConnectionString connectionOptions, String
>> > newPassword,
>> > Boolean redirectedUserInstance)
>> > at
>> > System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
>> > connectionOptions, Object providerInfo, String newPassword,
>> > SqlConnection
>> > owningObject, Boolean redirectedUserInstance)
>> > at
>> > System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
>> > options, Object poolGroupProviderInfo, DbConnectionPool pool,
>> > DbConnection
>> > owningConnection)
>> > at
>> > System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection
>> > owningConnection, DbConnectionPoolGroup poolGroup)
>> > at
>> > System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
>> > owningConnection)
>> > at
>> > System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
>> > outerConnection, DbConnectionFactory connectionFactory)
>> > at System.Data.SqlClient.SqlConnection.Open()
>> > at
>> > Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo
>> > ci, IServerType server)
>> > at
>> > Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
>> >
>> >
>>

Connecting to Reporting Services Server failed!!!

SQL Server 2005 and SSRS 2005 is curently installed on the same box. The OS is Windows 2003 (S) enterprise edition.

When I connect to the Reporting Services Server using the Sql Server Management studio I get the following error message

The request failed with HTTP status 407: Proxy Authentication Required.

(Microsoft.sqlserver.Management.UI.RSClient)

rsAccessDenied

I am tring to connect using the Windows Admin id. I would like to get an answer from this form.

-Aza

Any body to help here

-Nitu

Connecting Securely?

Hi,
I have SQL Server 2000 running on one box and IIS running on another box. I
am connecting to the SQL Server via ASP pages on the IIS box. My concern is
security -- currently I am using this kind of code to connect:
var setListings = Server.CreateObject("ADODB.Recordset");
setListings.ActiveConnection =
"Provider=SQLOLEDB.1;Password=PASSWORD;Persist Security Info=True;User
ID=USERID;Initial Catalog=tableName;Data Source=127.0.0.1"
My concern is that the username and password are being sent via plain text
from one box to the other.. Is this in fact the case? Is there another way
to make the connection? I think I could use Windows 2000 user accounts but
that would require trusted domains, etc. and neither box is a domain
controller (they are running at my ISP)
Thanks,
RichYou want to enable SSL for communication between the servers.
http://support.microsoft.com/defaul...kb;en-us;276553
-oj
http://www.rac4sql.net
"Richard Morey" <rwmorey71@.hotmail.com> wrote in message
news:ONWK0C4CEHA.2908@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have SQL Server 2000 running on one box and IIS running on another box.
I
> am connecting to the SQL Server via ASP pages on the IIS box. My concern
is
> security -- currently I am using this kind of code to connect:
> var setListings = Server.CreateObject("ADODB.Recordset");
> setListings.ActiveConnection =
> "Provider=SQLOLEDB.1;Password=PASSWORD;Persist Security Info=True;User
> ID=USERID;Initial Catalog=tableName;Data Source=127.0.0.1"
> My concern is that the username and password are being sent via plain text
> from one box to the other.. Is this in fact the case? Is there another way
> to make the connection? I think I could use Windows 2000 user accounts but
> that would require trusted domains, etc. and neither box is a domain
> controller (they are running at my ISP)
> Thanks,
> Rich
>
>|||Hi,
I have quickly glanced at the link you provided and will read it more
closely later.. Quick question -- we have SSL on the web server, not on the
SQL Server - will this still work?
Rich
"oj" <nospam_ojngo@.home.com> wrote in message
news:%230cwcK4CEHA.1128@.TK2MSFTNGP11.phx.gbl...
> You want to enable SSL for communication between the servers.
> http://support.microsoft.com/defaul...kb;en-us;276553
> --
> -oj
> http://www.rac4sql.net
>
> "Richard Morey" <rwmorey71@.hotmail.com> wrote in message
> news:ONWK0C4CEHA.2908@.TK2MSFTNGP09.phx.gbl...
box.
> I
> is
Server.CreateObject("ADODB.Recordset");
text
way
but
>|||SSL will have to be (at least) on sqlserver box for it to work.
-oj
http://www.rac4sql.net
"Richard Morey" <rwmorey71@.hotmail.com> wrote in message
news:%23fmWqq5CEHA.3344@.tk2msftngp13.phx.gbl...
> Hi,
> I have quickly glanced at the link you provided and will read it more
> closely later.. Quick question -- we have SSL on the web server, not on
the
> SQL Server - will this still work?
> Rich
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%230cwcK4CEHA.1128@.TK2MSFTNGP11.phx.gbl...
> box.
concern
> Server.CreateObject("ADODB.Recordset");
> text
> way
> but
>

Connecting PortalVB ?

When I try to install PortalVB (IBuySpy) it says "Database Server Instance" and a dropdown box saying "localhost".
That should be correct right?
I click 'Configure' and it doesn't work?

Anyone help?

Cheers,
Noth

Ps. I have MSDE installed.just a guess... Might be a login issue...

Connecting a SQL-DMO 7 client program to a sql 2K server

Hi,
We are running a client program on NT 4 using SQL-DMO objects. We have
upgraded the server (on another box) from NT4/Sqlserver 7 to WS
2003/Sqlserver 2K. Our Sql-DMO program is now returning an error.
We would like to avoid to upgrade the NT4 client box for stability reasons.
The doc is unclear to say if the sql-dmo 7 is compatible with sqlserver 2K.
Does somebody as tested this configuration ? What can we test to track down
this problem ?
Thanks in advance for your help.
Hi
DMO v7.0 is not compatible with DMO 2000.
You need to upgrade in any case due to the end of support for NT 4.0 by
Microsoft.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Phil" <PhilG@.newgroups.nospam> wrote in message
news:2CE0791B-7D6F-4160-BC7B-CA87C469AF99@.microsoft.com...
> Hi,
> We are running a client program on NT 4 using SQL-DMO objects. We have
> upgraded the server (on another box) from NT4/Sqlserver 7 to WS
> 2003/Sqlserver 2K. Our Sql-DMO program is now returning an error.
> We would like to avoid to upgrade the NT4 client box for stability
> reasons.
> The doc is unclear to say if the sql-dmo 7 is compatible with sqlserver
> 2K.
> Does somebody as tested this configuration ? What can we test to track
> down
> this problem ?
> Thanks in advance for your help.

Connecting a SQL-DMO 7 client program to a sql 2K server

Hi,
We are running a client program on NT 4 using SQL-DMO objects. We have
upgraded the server (on another box) from NT4/Sqlserver 7 to WS
2003/Sqlserver 2K. Our Sql-DMO program is now returning an error.
We would like to avoid to upgrade the NT4 client box for stability reasons.
The doc is unclear to say if the sql-dmo 7 is compatible with sqlserver 2K.
Does somebody as tested this configuration ? What can we test to track down
this problem ?
Thanks in advance for your help.Hi
DMO v7.0 is not compatible with DMO 2000.
You need to upgrade in any case due to the end of support for NT 4.0 by
Microsoft.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Phil" <PhilG@.newgroups.nospam> wrote in message
news:2CE0791B-7D6F-4160-BC7B-CA87C469AF99@.microsoft.com...
> Hi,
> We are running a client program on NT 4 using SQL-DMO objects. We have
> upgraded the server (on another box) from NT4/Sqlserver 7 to WS
> 2003/Sqlserver 2K. Our Sql-DMO program is now returning an error.
> We would like to avoid to upgrade the NT4 client box for stability
> reasons.
> The doc is unclear to say if the sql-dmo 7 is compatible with sqlserver
> 2K.
> Does somebody as tested this configuration ? What can we test to track
> down
> this problem ?
> Thanks in advance for your help.

Connect to SQL Server dialog box

I am studying the MCP book, and in Ch 10 (regarding SQL
authorization) it says:
The user name and password are submitted to SQL Server
2000 in clear text unless both the client and the server
Net-Libraries are using SSL encryption for the
entire session.

>--Original Message--
>Does anyone know if the SQL Server connection dialog box
transmit the password in clear text? I know it's hidden
from display but I'm wondering what it does behind the
scenes.
>Thanks,
>Ray Kurpiel
>.
>
Thanks for the response, Meryl.

Connect to SQL Server dialog box

I am studying the MCP book, and in Ch 10 (regarding SQL
authorization) it says:
The user name and password are submitted to SQL Server
2000 in clear text unless both the client and the server
Net-Libraries are using SSL encryption for the
entire session.

>--Original Message--
>Does anyone know if the SQL Server connection dialog box
transmit the password in clear text? I know it's hidden
from display but I'm wondering what it does behind the
scenes.
>Thanks,
>Ray Kurpiel
>.
>Thanks for the response, Meryl.

Connect to SQL Server dialog box

Does anyone know if the SQL Server connection dialog box transmit the password in clear text? I know it's hidden from display but I'm wondering what it does behind the scenes
Thanks
Ray KurpielI am studying the MCP book, and in Ch 10 (regarding SQL
authorization) it says:
The user name and password are submitted to SQL Server
2000 in clear text unless both the client and the server
Net-Libraries are using SSL encryption for the
entire session.
>--Original Message--
>Does anyone know if the SQL Server connection dialog box
transmit the password in clear text? I know it's hidden
from display but I'm wondering what it does behind the
scenes.
>Thanks,
>Ray Kurpiel
>.
>|||Thanks for the response, Meryl.