Mar 07 2017 03:34 AM
For one of our customer we have implemented a BCS based solution in Office 365. All is working however the external lists are very slow. ( somethign like 20 seconds to collect infromation);
Does anybody else have any experience with BCS in Office 365 connecting to an on-premises SQL database?
Miscrosoft support has been involved and they say that this is expected behaviour.
Keypoints from Microsoft:
If point 1 was true then I would expct to see a huge varation during the day/night.
If point 2 was true then I would expect that nobody would implement BCS. I can understand that it would take some time to collect information but not 20 seconds or more. We found that all CRUD operations are slow.
Mar 07 2017 07:26 AM
Hi Pieter,
have not used BCS for a long long time cause of timeing issues. better would be to create a seperate app/webservice. and include in SharePoint Framework 🙂
Mar 07 2017 07:27 AM
Mar 07 2017 07:37 AM
Mar 08 2017 01:29 AM - edited Mar 08 2017 01:49 AM
I wrote up the details on my blog and a uservoice
https://veenstra.me.uk/2017/03/07/office-365-bcs-performance-issues-dont-use-it/
Mar 08 2017 01:47 AM
Several years ago, I used BCS with a web service to get data and I don't remember it being that bad, it was not snappy but I seem to recall getting several thousand records in a few seconds. You may want to reach out to @Brett Lonsdale at Lightning Tools to see if they have any suggestions.
Mar 08 2017 01:48 AM
Hi @Dean_Gross, was this on-premises? For us it works fine in an on-premises environment but in Offic e365 it is very poor
Mar 08 2017 01:52 AM
Mar 08 2017 03:49 AM
Hi @Dean_Gross,
Do you remember the size of your tables? We now found that tables that are narrow ( 2-3 columns seem to work ok, not great but ok). Wider tables seem to be very slow.
Mar 08 2017 08:58 AM
I think it was 8 or 10 fields,