Unstable network environments
Posted: Wed 11 Apr 2012 22:00
Hi All,
Let me lay out the scenario we're facing and get your input.
We're currently on SDAC 4.x, working with a very large application. In our application we use a single MSConnection, and thousands of query objects throughout the application. Some at design-time, many at run-time. Some running for only a moment, others open for the entire time the application is open. So with that there are MANY DataSets that are open practically from initialization all the way through to finalization.
Between all of the various places we use SDAC in the application, the is no consistent usage of FetchAll, CachedUpdates, etc. There is a mixture of ad hoc queries (ExecSQL), Tables, Queries, Stored Procs... You name, we're probably using it.
In one of the more recent help files, there is a document titled "Working in an Unstable Network." where you outline some ways to handle unstable connections and unexpected disconnects.
Is there any practical way to achieve a graceful/seemless reconnect using the 4.x series of SDAC components?
If not with 4.x, will upgrading to the latest 6.x SDAC suite, given the application design I mentioned above, allow us to more gracefully/seamlessly handle unanticipated disconnects?
Thank you in advance for your input.
Let me lay out the scenario we're facing and get your input.
We're currently on SDAC 4.x, working with a very large application. In our application we use a single MSConnection, and thousands of query objects throughout the application. Some at design-time, many at run-time. Some running for only a moment, others open for the entire time the application is open. So with that there are MANY DataSets that are open practically from initialization all the way through to finalization.
Between all of the various places we use SDAC in the application, the is no consistent usage of FetchAll, CachedUpdates, etc. There is a mixture of ad hoc queries (ExecSQL), Tables, Queries, Stored Procs... You name, we're probably using it.
In one of the more recent help files, there is a document titled "Working in an Unstable Network." where you outline some ways to handle unstable connections and unexpected disconnects.
Is there any practical way to achieve a graceful/seemless reconnect using the 4.x series of SDAC components?
If not with 4.x, will upgrading to the latest 6.x SDAC suite, given the application design I mentioned above, allow us to more gracefully/seamlessly handle unanticipated disconnects?
Thank you in advance for your input.