Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It depends on so many things, not least the developer. I always think that a good developer with poor technology can produce a better product than a poor developer with cutting edge technology.</p> <p>There are many variables which matter in making a decision to migrate. For example:</p> <ul> <li>Is you current database running on a server or a local machine? I've worked for big companies who have servers which are always running out of space. This can really slow down performance. Running locally with lots of memory will always be faster.</li> <li>When you run these rules, do the tables get used in queries or in code? Is it optimised? Are there many levels of queries which it has to go through. Try cutting them down.</li> <li>If there is lots of VBA in the database, try putting lots of debug.print in the code with a timer on it so you can see what parts of the process are running fast\slow.</li> <li>Is there anyone accessing the database while it's running?</li> <li>Do you need to index the tables? Sometimes too much indexing can affect performance especially if it's not required.</li> <li>Maybe you can try normalising elements of your file when it's imported and then run the rules.</li> <li>If the database isn't currently split into a Front End - Back End, try splitting it. Maybe it's too big (compact and repair).</li> </ul> <p>As you mentioned in your post, there are many variables at stake so I wouldn't rush into a migration. Trust me, I've seen it before and there is no guarantee you will get a significant improvement without careful analysis of your current situation.</p> <p>One other thing you could consider rather than migrating, is automation. I worked in a RAD team which ran lots of early morning processes. We simply used Windows Scheduled Tasks to fire up a database at some specific time, search and import files, and then process them. Some processes may have taken a hour but they were all done before we got into the office in the morning so who cares if it took an hour so long as it was complete.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload