# High SQL load since Update

**URL:** <https://help.nextcloud.com/t/high-sql-load-since-update/43588>\
**Category:** ℹ️ Support\
**Tags:** github\_issue\_exists, nc14\
**Created:** [December 19, 2018, 4:00pm UTC](https://help.nextcloud.com/t/high-sql-load-since-update/43588 "2018-12-19T16:00:01Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![afleischer](https://help.nextcloud.com/letter_avatar/afleischer/32/5_5575768a8748004e209b776fc1b2916d.png) [@afleischer](https://help.nextcloud.com/u/afleischer)\
**Post date:** [January 6, 2019, 6:08pm UTC](https://help.nextcloud.com/t/high-sql-load-since-update/43588/7 "2019-01-06T18:08:30Z")

</div>

I’ve got the same problem here.

It looks like lookup\_server\_connector tries to update user data on [lookup.netcloud.com](http://lookup.netcloud.com). It hooks “User changed” and it looks like it’s also triggered if users synced from LDAP. Got around 300k entries in oc\_jobs here (udated some days ago to NC14). The [lookup.nextcloud.com](http://lookup.nextcloud.com) server seems to be down.

All federation options are set inactive in admistrative options here. Why it is syncing ? “occ app:disable” doesn’t work für lookup\_server\_connector, so I removed the folder in apps and deleted all entries of the LookupServerConnector class in oc\_jobs.

Filed a bug report: [https://github.com/nextcloud/server/issues/13396](https://github.com/nextcloud/server/issues/13396)

---

_[View the full topic](https://help.nextcloud.com/t/high-sql-load-since-update/43588)._
