Simplicty and flexibility!
Cart | |
Contact
| Download | Register| Sign In


Slow calculations on 2011 Small Business Sever with using SMB2


Started by
Search
You will need to Sign In to be able to add or comment on the forum!

Slow calculations on 2011 Small Business Sever with using SMB2

DataEase 8.2

I have a DataBase that contains a CashBook with @200,000 records

In the cashbook there are two fields Credit & Debits

Within a Form I have two lookup fields linked by relationships that need to calculate

Sum of Credit – sum of Debits.

On my laptop & home computer (both standalone Windows 8) this takes @ 2 seconds.

On my office computer this same DQL this takes over @10 minutes but quite often gives an error DataEase Not Responding and the screen whites out.

On all computers:-

I have changed in Application Preferences : Application Data Administration so that Locking Application is Opportunistic

With the application closed

File ; Options : DataBase Engine : I have un-ticked Share Local Database& have set Strategy to Opportunistic

On the Laptop & Home computer the database is on the same drive as the program, on the server the database is on a different drive ( but even if it is on the same drive it makes no difference)

The server has Server Message Block version 2 and runs on 2011 Small Business Server

Has anyone else experienced this problem & if so how do you overcome it???

Graham


Written by 17/10/14 at 12:15:23 Dataease [{8}]FIVE

Re:Slow calculations on 2011 Small Business Sever with using SMB2

It is hard to diagnose this without sitting on top of the problem.

For a very long time it was a speciality of DataEase support to work on the notion of conflicts, registry settings, patching and wizardry… I used to work on DataEase support in the early 90ies with DFD and Express and it was my experience then that it problems was 99.99% application design or real bugs in DataEase, and only very very rarely down to these conflicts, settings etc.

There is a big difference between a networked drive and a local drive but I see that you have the same problem if you run it locally on the server too.

  1. When you run it on the save drive as DataEase, does it run against a share or does it run directly against the directory.
  2. What is the drive letter of the drive? C: D: F:
  3. If you switch SharedLocalDatabase off then it will not use any form of locking on a local drive. However a local drive in DataEase terms is only a drive that has a drive latter between A: and E:
  4. If you switch SharedLocalDatabase off then you cannot share the database with other users or even yourself.
To be honest I think we are barking up the wrong tree here. We can spend time on establishing if the driver on the server is a “server drive” or a local drive, but I am pretty sure that the problem is that for some reason DataEase perceive it to be a server drive (and so do the server) and hence things will be slower. Something that takes 2 seconds on a standalone computer will quickly take much longer when it is done on a server drive.

The fact that you get the message “DataEase not responding” only means that Windows have perceived this process to take “too long” something you have already established for yourself. It really doesn’t mean anything else, and it is not a bug etc.

The problem is more that DataEase can be extremely quick on things it should be extremely slow on as long as you run on a local drive and have enough memory etc.

You say:In the Management Cashbook both Credit & Debit are indexed.

These are the fields that you are looking up (summarizing) and they DO NOT form part of the relationship so indexing them is “meaningless”.

Your relationship is based on Ref and Bal. These are the fields that need indexing in Management Cashbook.

The “DataEase Not Responding” message indicates that you use a lot of memory i.e. calculations and this is because your search is not optimum.

DataEase try to make the best Query possible but it is only a stupid software product so to get the best result you need to manipulate it.

The best way for you to get this to work fast in a network environment is simply to create a new field in both Bank Account Quick Balance and Management Cash Book where you make a “compound index field”.

New field: MyIndexfield.
Derivation: concat(Ref,bal) and index this field.

Then you build AccountBal on this field instead.


Written by DataEase 20/10/14 at 19:10:12 Dataease [{8}]FIVE

Re:Re:Slow calculations on 2011 Small Business Sever with using SMB2


Written by Graham Brown 22/10/14 at 13:28:50 Dataease [{8}]FIVE
DG3_ForumList