Fat Client (2-tier) Connections
From: YGeek (YGeek_at_discussions.microsoft.com)
Date: 03/23/05
- Next message: Jerommeke: "Adding relationships between tables using ADODB and ADOX"
- Previous message: Mr Not So Know It All: "How to Update an Oracle Stored Procedure with ADO and ASP"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Mar 2005 08:47:05 -0800
If I am developing a 2-tier system where an application talks directly to a
SQL Server 2000 database, what is the best practice for connections. This is
a manufacturing system with a limited number of clients that talk to a
dedicated server. I have heard some people state that opening a single
connection when the application starts is the best approach (obviously with
code to handle the possibility of dropped connections) while other people
state that the client should open a connection each time it needs to talk to
the server. I would really like an explanation of which approach is better
and why it is better than the other approach.
On a similiar note, if I choose the solution where I use one connection when
the application starts, will that connection eventually be closed by the
server if it is inactive for a certain period of time? I'm not sure how SQL
Server 2000 handles connection and I'm wondering if the server will
automatically drop inactive connections to free resources. I have been
unable to find any information on how SQL Server 2000 handles inactive
connections.
Thank you for your help and your time!
Regards,
Brian
- Next message: Jerommeke: "Adding relationships between tables using ADODB and ADOX"
- Previous message: Mr Not So Know It All: "How to Update an Oracle Stored Procedure with ADO and ASP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
