Disconnected Architecture...help!

FAQ

Profile

Disconnected Architecture...help!

Database Help (Home) -> Connect

Next: Between Question

Author

Message

Nab

External

Since: Feb 16, 2005
Posts: 4

(Msg. 1) Posted: Wed Feb 16, 2005 3:58 pm Post subject: Disconnected Architecture...help! Archived from groups: microsoft>public>sqlserver>connect (more info?)

If ADO .Net supports disconnected architecture why do we have to close a connection after we open it? Isn't ADO .Net supposed to do that automatically since it supports the disconntected architecture? Why is it that i don't have to open a connection (by writing e.g. Conn.Open) after i establish a connection visually through the Server Explorer? Does the establishing a connection through the Server Explorer automatically opens the connection? Any insights on these matters will be highly appreciated by this novice. >> Stay informed about: Disconnected Architecture...help!

Display posts from previous:

Related Topics:

Cannot generate SSPI context - Hi All, I am experiencing problems with a remote user (w2k pro,sql 7) attempting to connect and replicate with a Sql Server 7 on NT server. They are receiving 'Cannot generate SSPI context' messages when trying to use a vb app over a vpn. This problem..

connection string does not work for a different server - Hi all, I currently have an ASP .Net project running locally, and accessing a local SQL server 2000 database. The project runs fine since it is able to open the connection to the database, and perform operations on it locally using a connection dtata..

IIS 6 and Windows Authentication to SQL Server 2000 - I am running a Windows Server 2003 machine as my web server. I would like to use Windows authentication for connections to my SQL Server 2000 instance on a Windows 2000 server. I've read where mirroring the ASPNET account and password on the web server...

SSL Security error -ConnectionOpen(SECDoClientHandshake) - Please help. On my default instance of SQL Server 2000, which could be accessed OK with both Windows and SQL server authentication, I now get the error in the subject line above. The message in the error window - in SQL server enterprise manager- suggest...

Connecting client to SQL Server via Cisco VPN - We are having one client PC running Win XP. SQL Server has been set to Windows Authentication, TCP/IP 1433, Windows 2003 (!). Via Cisco VPN we are making a connection. IAS has been configurated, so the local user profile doesn't matter. The server..

	Database Help (Home) -> Connect	All times are: Pacific Time (US & Canada)
Page 1 of 1

You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum