Forum Discussion
SQL Server Vs SharePoint for building Power Apps standalone
We want to start a new project for audit management:- 1) the system contain these main entities and the relation between them:- - Project - TaskList. One Project can have many TaskList. and one Ta...
john john If your customer is willing to spend on premium licenses needed for the SQL connector, then I would add a 3rd option - dataverse. There is a bit of a learning curve in getting things set up, but you should be able to achieve everything you outlined in the high level requirements.
The SharePoint connector can be slow at times and I have seen response times of up to 90 000ms at times. However if additional premium licenses is not an option then this is your only option.
Abdurahman_Jardinebut why you prefer dataverse over sql server?
john johnI wouldn't say I prefer it. It is another option to consider. It depends on the use case and the infrastructure.
1 simple example would be if you need to spin up a SQL environment to meet your requirements then you have to consider the license costs around SQL as well ontop of the power platform premium licenses per user. Where the dataverse provides a relational database capability natively if the users are licensed for premium.