HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SQL 2000 client connectivity
Operating System - HP-UX
1828575
Members
2179
Online
109982
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2004 11:36 PM
02-24-2004 11:36 PM
SQL 2000 client connectivity
Hi,
We have a requirement to test connectivity of clients to the SQL 2000 database. I am very new to this :-( ... well, what I need to accomplish is when the database is running all the clients should be able to connect to it also when the SQL system goes down for some maintenance the clients should not abort the connection but should keep on trying to reestablish the connection. Once the SQL server comes back online the clients must be able to reconnect to the database with out any intervention.
My questions are,
1.) What is the client software required to accomplish this?? I also need to know if it is possible to set a timeout period for the reconnection to the database.
2.) Does the default Client tools that come with SQL2000 support this kind of re-connection?
3.) What happens to the transaction that might be happening when the server goes down? Can we recall/recover these transactions?
Please help.
Thanks,
Karthik S S
We have a requirement to test connectivity of clients to the SQL 2000 database. I am very new to this :-( ... well, what I need to accomplish is when the database is running all the clients should be able to connect to it also when the SQL system goes down for some maintenance the clients should not abort the connection but should keep on trying to reestablish the connection. Once the SQL server comes back online the clients must be able to reconnect to the database with out any intervention.
My questions are,
1.) What is the client software required to accomplish this?? I also need to know if it is possible to set a timeout period for the reconnection to the database.
2.) Does the default Client tools that come with SQL2000 support this kind of re-connection?
3.) What happens to the transaction that might be happening when the server goes down? Can we recall/recover these transactions?
Please help.
Thanks,
Karthik S S
For a list of all the ways technology has failed to improve the quality of life, please press three. - Alice Kahn
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2004 03:39 AM
03-01-2004 03:39 AM
Re: SQL 2000 client connectivity
Hi,
Below is a htm link to some SQL2000 Online help documents:-
mk:@MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\trblsql.chm::/tr_rptconsetup_5gmr.htm
The documents discuss Sql2000 Connectivity and specifically what happens to orphaned processes, and more importantly how to prevent them using :-
KeepAliveTime for TCP/IP
SessionKeepAlive for NetBios
This is a useful start point and should get you on the way.
Keith
Below is a htm link to some SQL2000 Online help documents:-
mk:@MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\trblsql.chm::/tr_rptconsetup_5gmr.htm
The documents discuss Sql2000 Connectivity and specifically what happens to orphaned processes, and more importantly how to prevent them using :-
KeepAliveTime for TCP/IP
SessionKeepAlive for NetBios
This is a useful start point and should get you on the way.
Keith
You are either part of the solution or part of the problem
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP