UpdateBatch or Update w/Stored Procedure (Database via Wireless Network)
From: Brad H McCollum (bmccoll1_at_midsouth.rr.com)
Date: 06/02/04
- Next message: Val Mazur: "Re: Deadly slow code ... where am I screwing up"
- Previous message: Dale: "Re: Deadly slow code ... where am I screwing up"
- Messages sorted by: [ date ] [ thread ]
Date: 2 Jun 2004 15:07:00 -0700
I'm working on some application development for a client who has a
small office operating on a 54 mbps wireless network.
I'm using VB 6.0 for the GUI, Crystal Reports for the reporting piece
of the application, and the data is stored on the server in a SQL
Server 2000 (actually, MSDE) database.
When the application is used directly from the server, the performance
is just fine.
However, the issue arises when any of the users on the remote PCs
connecting to the database via the 5 mbps wireless connection.
The navigation through the records in various forms is pretty fast, as
I'm working with disconnected recordsets.
Here's the issue of concern/question... what's likely the best and
most efficient way to update/insert records back to the production
database wirelessly via the server.
I've tinkered with two methods of doing this and both (of course) have
their good points and bad points.
(1) I've tried passing each changed record back to the database using
insert/update stored procedures and passing all of the field values
back to the database. This works fine and instantly updates each
record that the user changes, but the cost of doing this is a
longer-than-desired delay in the movement from one record to the next
in the form the user is looking at due to the compromising of speed
across the wireless network while the stored procedure is executed.
(2) I've also tried just making all inserts/updates to the local
disconnected recordset and then using UpdateBatch to update all
appropriate records to the production database once the user has
closed out of the form. This works fine as far as speeding-up the
user's navigation from one record to the next while the form is open
on their machine. The downside, of course, is that it sometimes takes
a while for all of the updated/inserted records to be passed back
across the network all at once when the user closes the form. The
user is then sitting there wondering when the form is ever going to
close.
I'm at a loss of the best scenario here. If anyone else has any
experience with operating databases across a wireless network and the
situation of either using insert/update stored procedures to update
the records one-by-one as they're navigated off of, or just making the
updates/inserts to a local disconnected recordset and taking the
performance hit at the closing of a form by doing UpdateBatch via ADO,
I would welcome any recommendations, code examples, sugggestions,
points towards other good sources of info. on the Internet, etc.
Thanks!
Sincerely,
Brad McCollum
bmccoll1@midsouth.rr.com
- Next message: Val Mazur: "Re: Deadly slow code ... where am I screwing up"
- Previous message: Dale: "Re: Deadly slow code ... where am I screwing up"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
