Unanswered

Sync SQL table into CDS - Can do?

(0) Share

Report

Posted on by martinav

3,347

Subject pretty much explains it. I have an on-premesis sql table of about 2500 items. I want to push it up to CDS, so I can get to it quicker in powerapps. Can do? I also want it to stay sync'd. One-way. The on-prem will always be the table getting new data. No need to change it in CDS.

What think you?

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Sort by

v-monli-msft Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi @martinav,

Yes, you can add data from SQL to an entity in Common Data Service for Apps by using Power Query. You can also filter, transform, and combine data before you load it into a new or existing entity. For detailed steps and information, please have a look at:

https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/data-platform-cds-newentity-pq

I suggest that you load the data to a new entity. If you use Power Query to add data to an existing entity, all data in that entity will be overwritten.

For the future data syncing, you could use a Flow like below to achieve this.

Regards,

Mona

Was this reply helpful? Yes No
martinav 3,347 on at

Like (0)

Report
Copy link

Link copied!

Are there any limitations to the CDS entity (table)? Like database size in bytes, or number of records?

Plus, what might I expect for my complex lookups as a performance improvement?

Is this a good way to do this?

Was this reply helpful? Yes No
martinav 3,347 on at

Like (0)

Report
Copy link

Link copied!

I'd like to refresh this a bit. I do need to know if there are performance gains expected using CDS over an on-prem gateway SQL table(s). It has been a bit of a chore to do an initial dump of tables into CDS. Getting errors. Thats not my quesiton here, but is it even worth my effort. I have many complex calls to SQL tables throught my on-prem gateway that is making my app quite slow. Plus, I'm the only one using it. There will be 10+ using it when it goes production. Please advise on this, or other ways to improve performance.

Things I have done to improve speed:
- Create views from SQL tables, to reduce the number of nested loop filters, and complex and/or search criteria.
- Redesigned interface to pull in data to a reduced set of results.
- Limited search results, requesting user to tighten their search

Was this reply helpful? Yes No