Hi Johanna,
Unfortunately I can't help you explain the gradual slow down during a
longer edit session.
But I do have experience with databases (not SQL Server but PostgreSQL)
in a network and my recommendation is to always have QGIS in the same
network than the database. Having the database in the cloud and QGIS in
the LAN of your organization with a slow network link in between will
result in bad performance due to network latency. In the long run, I
would try to either bring the database to the same LAN within your
organization to avoid network latency, or alternatively run QGIS desktop
in the same network/cloud where your database is located. There are
still functions in QGIS where certain database operations are processed
one feature at a time and network latency makes this much worse. The
developers are though trying to eliminate such feature by feature
processing in favour of processing whole batches at once, which improves
the situation with slow network connections.
If, for some reason you need the same database in two different
locations, then I would introduce two database installations local to
the respective networks and use replication in between to keep the data
in sync. This reduces the network latency issues significantly.
Andreas
Am 05.05.20 um 08:51 schrieb Johanna Botman:
Hi,
I have a situation where there are three of us using QGIS v3.4
connecting to a Microsoft 2016 SQL Server to add and edit items to
tables in the same database at the same time. And I’m growing old
waiting for things to happen.
When we were all in the office, we connected through the work network
to the databases in the cloud and suffered some issues with delay that
may be caused by internet speed. Now that we are all working from
home, we have the added complexity of connecting to our home Wi-Fi
then a VPN to the office before we then go out to the cloud.
But now the bottom line is that no more than one user at a time can
edit the tables. Responses are painfully slow and by mid-afternoon,
QGIS is completely unresponsive.
Users love to blame the software. That’s what they are interacting
with, but I don’t believe that it is all QGIS’ problem. I’d prefer to
blame a database that appears to not respond well to a multi user
environment.
Does anyone have any ideas, or strategies, to troubleshoot?
**
**
*Johanna Botman*
Assets / GIS Officer – Melton City Council
***********************************************************************************
The information in this message is privileged and confidential,
intended only for the use of the individual or entity named above. If
you are not the intended recipient you are hereby notified to delete
the message and that any dissemination, copying or use of its content
is strictly prohibited. If you have received this message in error
please notify the Melton City Council.
***********************************************************************************
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
