Showing results for 
Search instead for 
Did you mean: 
Kudo Kingpin
Kudo Kingpin

SQL guys : why don't we use CDS ?

Hey folks,

Having been more involved on these forums for the past few weeks, I realized there are quite a few SQL Guys like me around. (I thought I was an oddity)

Until recently, there was a gentle "live and let live" attitude between SQL and CDS. We didn't get much love (see the ideas on triggers or procs) but we were more or less free to do our own things in a nice cost-efficient manner. Now, with the new licensing, the attitude has switched to a much less subtle "convert or die" message... with the expected pushback from the community as a result.

Yet some folks at MS are curious about why we won't use CDS as our go-to data storage. I have my own reasons, which I'll share in the next post, but I'm curious about yours. Are you able to explain why you simply won't switch to CDS overnight? Obviously, I don't believe the "all-in on CDS" strategy is going to change anytime soon. The goal here is to provide insights and understanding to MS as to why we "resist" CDS (a genuine question I've been asked by different MS employees already).

To temper my comments, let me start by saying that I DO believe that CDS has a part to play in the Power Platform. It's a great low-code DBMS sitting somewhere between Sharepoint lists and full Az SQL DB as a backend option, not unlike front-end sophistication can vary between highly managed model-driven screens all the way to PCF components. As far as I can tell, CDS' main value proposition is : 

  • No need to learn SQL (not an advantage to us, but will be for some)
  • Common model with Dynamics (if your client uses that)
  • Native REST API querying, something vanilla Azure SQL DB doesn't offer

@PaulD1 @MrMarshall  @MagnusGöransson @WillPage @OneThing @NEPatton @Rick72 @AngryBatVoice @sscarcella @digiservice @opit @JohnP @inverse70 @wjhepworth 

Kudo Kingpin
Kudo Kingpin

Now, my own two cents on the topic.

First, one has to realise that onboarding a new technology is a cost-benefits analysis. If we don't do it, it's because the benfits aren't justified by the costs.


I briefly touched on the fact that, overall, CDS currently lacks clear benefits for me. I'm well-versed in SQL and my clients don't use Dynamics. Proper modeling is so core to a good project that I won't just go for something generic unless I have a compelling reason to. And creating 5-10 tables (an average for a PowerApps project) is just not that long. So the argument of the "one-size-fits-all" of modeling just doesn't hold for me.


The list here is a bit long, so let me break it down.


Any new technology needs time to learn and to master. We need to develop best practices and good patterns for said technology. There was nothing broken with SQL for us to start with, so even if we would have feature parity between the two platforms, the learning costs alone would have me stay in SQL. It's not that major in the big picture, but it's worth keeping in mind.

Licensing fees

Lots of ink has been spilled over this, but there's a HUGE price difference in the two technologies. Most of my PowerApp project work just fine on an Azure SQL DB S1 (30$/month) with no extra storage since we already have 250 GB for that price. By comparaison, a CDS-based project is 10$/month/user + a wooping 40$/GB/month (vs 0.20$/GB/month for extra SQL storage).

Consider an average project of 50 users with a 3 years lifecycle (lets say no extra storage is needed), the price difference is 17K$ ! This alone kills my sales argument to client that low-code is great because it's faster/cheaper. Right now, full-blown custom dev by a senior consultant is cheaper... And that's a problem ! ^^

But enough has been said on this already.

Physical layer

Part of our job is making fast performing apps, and a big part of this is optimizing the physical layer of data. There's a big difference between a TINYINT and a BIGINT, between a VARCHAR and an NVARCHAR. And if you join tables on GUIDs, we're just not going to be friends. I need to place an index here and there, sometime add additional fields to cover a query and occasional materialize an entire view when it makes sense for the user experience. To the best of my knowledge, we don't have any control over that in CDS.

Complex querying

CDS views are nice, but I often need much more complex logic to represent common business problems. I need the expressivness of the T-SQL language for things like windowing clauses, pivoting data results, CTEs and paging with OFFSET/FETCH just to name a few. And I often need to upserts batches of lines at once with MERGE statements from a parsed JSON payload.

SQL programatic objects

I need strong T-SQL procedure support with transactions enabled, elegant error handling (beyond just bubbling up a system error) and dynamic SQL. On rare occasions, I need to temporairl elevate priveliges during a procedure in a controlled manner. Sometimes I need to materialize intermediary results in temporairy tables and the few times I've had to use CROSS APPLY on a table-valued function really saved my bum.

I understand we can add C# plug-ins to CDS, but my language is SQL...

Data Ops

Bringing CI/CD to a database project is quite the challenge ! Not only do you have to have deal with schema comparaisons, but you also have to deal with transitional changes of the data itself (it's a stateful system after all!) with pre/post deployment scripts.

CDS is improving in this area with solutions and CLI commands, but we're still worlds away from git-based SSDT projects with peer-reviewed pull-requests over an Az DevOps pipeline with automated testing of SQL programatic objects.


My projects don't live in isolation. We do BI on them, we exchange information with other systems and perform other various ETL work. Azure SQL DB inherits the hundreds of native SQL Server connectors to the outside world whereas CDS is still quite poor on this area. Power Query is nice enough to import data, permform light ETL work (more like data prep) and its got a great UX, but it doesn't cut it for serious industrial data pipelines. And yes, my PowerApps project sometimes import gigabits of data into their databases (that tend to be the case when we Papp as a light MDM/DQM tool for data stewards).

That's about the major parts for me. And you ? How do you feel ?

For me, the deal killers for CDS came down to the following:


  • The unecessarily complex implementation of relationships were very SharePointy and not very efficient.  I have not gone back and revisited.
  • While it is great we start with a whole lot of entities and relationships, I did not need any of them.  The areas where it supported what I needed was generic and required me to extend them.
  • Most Importantly - The Delegation limits were horrible!  Seriously, when you look at the delegation charts it seems like the CDS and SharePoint connector teams had to have gone on  vacation.  Simple function such as Average, Max, Min, Sum and IsBlank are all non-delgable on CDS (and SharePoint).  Compare that to SQL Server where nearly every function is delegable.  Simply put, the team that built and updated the SQL Server connecter are way ahead of all others.  No really, even the SalesForce connector is better.  

Just my $.02 after taxes.


Kudo Collector
Kudo Collector

The major one for me was just cost.  Feature- and function-wise, CDS might be the middle child between Sharepoint Lists and AzureSQL, but if that's its intended niche, someone forgot to inform the pricing people, because the license necessary for CDS was always just too far out of my reach to even consider it.  I'm a small team, working for a small company.  Just like with the new Powerapps and Flow licensing, even if I could use CDS to streamline and improve every single workflow in the company, we just aren't big enough to where those savings would justify the costs.  We simply don't have that kind of overhead. 

On the flipside, with SQL, I'd get a more robust product that I can leverage at an acceptable cost.


I honestly have not formed an opinion on CDS outside of the cost, because the cost eliminates it as a possibility for me.  I'd happily try it out, but at the price-point they have it at, it'd be a waste of time because it isn't something I'd be able to sell to the ownership.

Not applicable

@AngryBatVoice  @FredericForest  @wjhepworth  Moving to CDS board 


More or less the same sentiments from us.


CDS would be great is all our systems were in Dynamics. The Built in entities would be easily shared and accessed across products and the ability to add the them would be useful.


However Dynamics change of prices had again prices itself out of our budget so there has been no further investigation. 


Almost all of our systems are independent and living on their own SQL databases. The ability for us to join these in AzureSQL and built upon the shortcomings of each platform is where our real benefit lies. 

My feelings on CDS?

I think it's awesome.  I like the concept and power it offers - for where it is the righ solution.  I could see how CDS is usable/valuable even game changing for some organizations/departments/businesses.


Why don't I use CDS?

I work in a manufacturing facility.  To build a modern manufacturing environment - you have to be able to connect equipment to the network and view the status of the equipment in real time and throughout history.  The equipment being connected is a huge hodge-podge - we have new equipment that we purchased within a few years, decades old equipment that we've retrofitted within the last decade, and stuff that we haven't been able to retrofit yet.  You have other non-equipment systems that you must interface with to effectively use your data:  Blue Mountain (Asset management software w/ SQL back-end), SAP, OSI PI DB/AF, MES, etc.


Long story short - I am trying to convert a manufacturing plant with over a hundred different data sources into (what appears to be, from the end user perspective) a single data source that allows for equivalent data comparisons/analyses across all hardware/software platforms, etc.  It is incredibly complicated to solve this problem - it requires capital expenses to strategically update hardware, it requires reprograming and redesigning equipment software architectures.  I have been working on this for 8 years now, and I still have a long way to go.


Anyone who tries to tell me that CDS can be a solution for what I'm doing (SUCCESSFULLY) at my plant does not understand what I do.  I have an open mind to new technologies - I am good at assessing the value of new technologies.  CDS is valuable!  So is snake venom! 


Valuable != Usable!


Great question, it's just simply not feasible at the moment @FredericForest 

The amount of data we have in various SQL deployments it would be fairly close to impossible to get everything in to a new form without a mammoth project. We have data coming in from legacy systems, third party systems and internal developments. 


We don't have the budget, resources or time to move the data stores. And the cost and horror of getting suppliers to move away from SQL also. 


I think in a utopian scenario we'd all have our infrastructure completely different and we could see where CDS might fit in that picture. But the size and complexity of this kind of change for an organisation like ours would just not have the ROI. 


The big value for us and I'd guess a fair few others was that the SQL connector meant we could plug in to everything else we already had so fluently.

Community Champion
Community Champion

To this point, our clients haven't shown any interest in CDS (largely due to cost I expect) so we haven't looked into CDS deeply, though we have done some projects with canvas apps connecting to Dynamics which I believe is a similar experience. Below are my thoughts, but please be aware I know very little about Dynamics/CDS so happy to be corrected/proven-wrong.


What I see in Dynamics (extended with additional entities) is some pretty horrible data modelling (same data in multiple entities) which I presume is because it is difficult to build performant queries on a normalised data model in CDS / Dynamics so data just gets repeated through multiple entities, though I stress this is speculation on my part.

Entities following the common data model have a gazillion fields - it is a real pain in PowerApps to figure out the correct one to use, especially as sometimes the internal name needs to be used and sometimes the 'freindly name'. Because there are so many unused fields, people start using them to store other data rather than create new fields which undermines the whole common data model approach.

In one project there was a desire to write data to a many-to-many relationship. This proved to be impossible (the child entity is invisible to PowerApps and Flow). We gave up and stored the data elsewhere.

When moving Dynamics from one environment to another (say Dev to Test) the environments frequently do not behave the same way - for example, one environment will want an entity use friendly names, the other internal names, one environment will extend out 'reference' fields (e.g. a UserID field will let you drill into the name, email, etc)., the other will not (e.g. returing only the ID). My knowledge of Dynamics is minimal, but I have seen this across several different customers whose Dynamics teams seem more than competent but are unable to get environments to behave consistently.



SQL is a know quantity, has great tools, is super powerful and flexible even supporting JSON and XML. There are good tools for tuning Views/Indexes to help you run efficiently and keep on the lower tiers of the subscription model. It is easy to separate out solutions into different DBs so it is easy to track of cost by App, do a restore from back-up by App if needed and so on. SQL DBs are easy to script out, so deploying to other environments is quick and simple.



In short, I'm much happier working in SQL and our customers haven't expressed interest in CDS. I guess CDS is easier/better than SQL for building business processes around the data, but so far for our customers that doesn't seem to be a compelling enough benefit to outwiegh the costs, though it is early days for CDS so that could change quickly.

Hey @PaulD1 ,
I get what you mean, I feel more or less the same way. I think the ease of navigating the CDM improves the more we use it, but the learning curve is certainly steep... and not very appealing if we don't need it outside of our PowerApps projects (which tend to be quite focused and specialized). Just a lot of noise for what we need, really. I does make sense however in a D365-based client were learning the CDM is part of the job anyway since there's going to be relevant data in it.

Moving to environments is also a big thing. I can't stress this enough : migrating from one environment to the next is not just about the schema, it's also about the DML scripts (pre/post deployment) to adapt the data.

And yeah, it's a real shame that you can't adress CDS using the SQL language (the de facto lingua franca of data), and T-SQL in particular (a nice version of it, which virtually all MS data professionals know by heart). REST endpoints are a nice bonus, but its not enough. It's like asking a chef not to use a knife to cook...

Helpful resources


Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders     UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: 2. Power Apps Copilot Cookbook Gallery:   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   Week 2 Results:  Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Users online (4,291)