Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 21 to 26 of 26 total |
CS Performance Problem from Remote Site |
Thu, May 1 2008 2:35 PM | Permanent Link |
Gordon Turner | John Hay wrote:
> > If your calcs are to complicated for an SQL statement you might need to > create a server side procedure. My calculation is way too complicated for an SQL statement (it actually involves a couple hundred lines of code with lots of date math, calls to sub-procedures, multiple queries, processing of result sets, etc). I was thinking about a server side procedure, but that involves a major re-write to the program and I was hoping to avoid that. -- Gordon Turner Mycroft Computing http://www.mycroftcomputing.com |
Thu, May 1 2008 3:21 PM | Permanent Link |
"Robert" | "Gordon Turner" <gordon@mycroftcomputing.com> wrote in message news:E1BAC4EC-88C4-4511-9CC1-AB421FC2AD09@news.elevatesoft.com... > John Hay wrote: >> >> If your calcs are to complicated for an SQL statement you might need to >> create a server side procedure. > > My calculation is way too complicated for an SQL statement (it actually > involves a couple hundred lines of code with lots of date math, calls to > sub-procedures, multiple queries, processing of result sets, etc). I was > thinking about a server side procedure, but that involves a major re-write > to the program and I was hoping to avoid that. > Keep in mind that you can transfer result sets to a local memory table if needed. The difference in speed is amazing. Also, look into the RemoteReadSize property, another one that can give you amazing speed improvements with little work. View the help file for more details. Robert |
Fri, May 2 2008 5:06 AM | Permanent Link |
"John Hay" | Robert
> Keep in mind that you can transfer result sets to a local memory table if > needed. The difference in speed is amazing. Also, look into the > RemoteReadSize property, another one that can give you amazing speed > improvements with little work. View the help file for more details. I was thinking about that. I would be concerned that if you have to update/insert a lot of records you are going to be hit by the latency issue anyway. Is there an equivalent of remotereadsize for updates/inserts ? John |
Fri, May 2 2008 9:15 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Gordon,
<< My calculation is way too complicated for an SQL statement (it actually involves a couple hundred lines of code with lots of date math, calls to sub-procedures, multiple queries, processing of result sets, etc). I was thinking about a server side procedure, but that involves a major re-write to the program and I was hoping to avoid that. >> It shouldn't more than about 30 minutes of refactoring. Just isolate the process to one unit with a single procedure or class (with methods) that can be called. Then, just call this procedure or class method(s) from the application or database server, depending upon whether the you're using a local or remote session. It's really just a bunch of "moving code around". This is what we do with our internal build system - it can be called locally for testing purposes, or from the database server for production purposes. If you need specifics, just send me the code and I'll give you a rough outline. However, make sure your support plan is paid up. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, May 5 2008 1:00 PM | Permanent Link |
"Rob Frye" | Hi John
> Is there an equivalent of remotereadsize for updates/inserts ? Not exactly but check out 'Cached Updates'. (BeginCachedUpdates, ApplyCachedUpdates, and CancelCachedUpdates methods) Rob |
Tue, May 6 2008 11:22 AM | Permanent Link |
"David Farrell-Garcia" | Gordon Turner wrote:
> Unfortunately, this is the CS version of a standard product I sell, > so I have no say about the customer's environment. But if they are > connecting at 10MB, I would not expect the application to take > minutes to load. It's not that big or complex - just the exe and one > DLL, and the exe is only a couple MB. You may not have a say, but if they want better perfomance I think they will need to consider options. If they are loading the application.exe remotely, I would bet that is the bottleneck. That is easy enough to test. -- David Farrell-Garcia Whidbey Island Software, LLC |
« Previous Page | Page 3 of 3 | |
Jump to Page: 1 2 3 |
This web page was last updated on Thursday, March 28, 2024 at 08:36 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |