cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Post Prodigy
Post Prodigy

CDS vs SQL - What to choose when?

Hello,

 

As CDS is becoming more and more rich and powerful day by day with many features and soon will provide the tsql support - I am little confuse on when to choose CDS and when to consider SQL database.

 

Can anyone please clarify this ?

 

Thanks,

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Super User II
Super User II

Re: CDS vs SQL - What to choose when?

Hi @dave8,

CDS is much more than just a database. It comes with a rich set of features that are usually common to any type of system/application especially in the enterprise space. If we were to compare to traditional software design, with a database, you'll need to develop a data access layer and all, however with CDS all that is taken care of out-of-the-box and the developers just need to focus on the business and presentation layer. We can refer to CDS as a platform and even SDaaS (Software Dev as a Service). Here are just a few examples of these capabilities that you would have to custom build yourself or use custom frameworks with SQL:

  • Data Management (import and export capabilities)
  • Reporting and dashboards for end-users
  • Users and Queue management
  • No code business logic client & server side
  • SDKs and APIs which automatically scaffolds on change of data model
  • Auditing and Logging
  • MS Office integration
  • Searching and querying
  • SharePoint integration
  • Currency management
  • Data Duplication Detection
  • Multi-language support
  • Pre-built UI template (model-driven apps)
  • MS Exchange integration
  • Administer and monitor, DevOps tools, console and admin center
  • Core data model (CDM aka Common Data Model) and schema out-of-the-box
  • Activities/Interactions management
  • and more 🙂

Hope this clarifies!

View solution in original post

1 REPLY 1
Highlighted
Super User II
Super User II

Re: CDS vs SQL - What to choose when?

Hi @dave8,

CDS is much more than just a database. It comes with a rich set of features that are usually common to any type of system/application especially in the enterprise space. If we were to compare to traditional software design, with a database, you'll need to develop a data access layer and all, however with CDS all that is taken care of out-of-the-box and the developers just need to focus on the business and presentation layer. We can refer to CDS as a platform and even SDaaS (Software Dev as a Service). Here are just a few examples of these capabilities that you would have to custom build yourself or use custom frameworks with SQL:

  • Data Management (import and export capabilities)
  • Reporting and dashboards for end-users
  • Users and Queue management
  • No code business logic client & server side
  • SDKs and APIs which automatically scaffolds on change of data model
  • Auditing and Logging
  • MS Office integration
  • Searching and querying
  • SharePoint integration
  • Currency management
  • Data Duplication Detection
  • Multi-language support
  • Pre-built UI template (model-driven apps)
  • MS Exchange integration
  • Administer and monitor, DevOps tools, console and admin center
  • Core data model (CDM aka Common Data Model) and schema out-of-the-box
  • Activities/Interactions management
  • and more 🙂

Hope this clarifies!

View solution in original post

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Tech Marathon

Maratón de Soluciones de Negocio Microsoft

Una semana de contenido con +100 sesiones educativas, consultorios, +10 workshops Premium, Hackaton, EXPO, Networking Hall y mucho más!

Users online (6,924)