Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.paradox    |    To crash or not to crash, asks Borland    |    9,834 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,882 of 9,834    |
|    Roy F to Craig    |
|    Re: I need help in asking the right ques    |
|    01 Nov 07 14:33:04    |
      From: roydoc@NOMORESPAMcox.net              Hi Craig,               >it slows down terribly....              Unfortunately this is the nature of file based databases. The larger the       size of your data tables, the slower your app becomes on a network.       Having said that, the way your app is written can either put off the       inevitable for a while or lead you to it faster. For instance, if your       app uses a lot of queries on network tables you are going to find it       slowing down sooner rather than later. If you can use secondary indexes       with set range to get the views of the data you need, things will happen       a lot faster. There are multiple things like that that can help or       hinder you depending on how you chose to approach it. How large are the       data tables on the network?              However even in the best of circumstances, the app will get       progressively slower as you get more data. If you are going to use this       app for any length of time and will keep adding a lot of data, the       answer is to convert the back end to a CS database. I've been there and       done that. I spent the last year converting a traditional Paradox app to       one which uses Paradox for the GUI and MS SQL server 2K for the       database. Everything runs off stored procedures on the server. The       difference is absolutely stunning. Things that used to take 30-45       seconds are now instantaneous. The improvement in speed is really       unbelievable. It is rock solid also. I know that's not what you wanted       to hear, but that has been my experience.              Regards,       RoyF              Craig wrote:       > For years my software has run quickly on a local drive but when there are       > large files on network drives, it slows down terribly when moving from       > record to record.       >       > I am going to approach our IT department about, but before I do, I need to       > know what questions to ask.       >       > My software is in a large hospital, but at this point it runs stand alone       > (not netowkred) using Paradox 10 Runtime. I think they use Novel network       > What are the factors which will slow down performance when a database runs       > on a network drive?       > I don't know where to start. I would like to get information, bring it back       > to this forum and ask for help in sorting this out. Has anyone else run into       > this problem?       >       > Thanks in advance       >       > Craig       >       >              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca