synapse sql pool design

Question

Hello,
In synapse workspace, we are using serverless sql pool in which we store config information, data, audit logging, etc in .parquet format and use views to read them...
Some team members are saying we should also use azure sql server to store details of config,, logging
Do you think we should really have both serverless sql pool and the azure sql server?
Thanks

Answer 1

Hello @arkiboys ,
Thanks for the ask and using Microsoft Q&A platform .

As I understand the ask is should the config information, data, audit logging, etc should also persisited in Azure SQL also ?

At this time we are not clear as to how the config information is used in your case , if its metadata is used by other ETL process and others process which does not need data at a fast blazzing speed then to me that should be just fine . In scenario , like these config data is used by a front end ( UI ) , cases like this I will be go with Azure SQL server . For all the audit data scenario I think I will say we should use serverless .

You should also consider that there is no charge for resources reserved in serverless , you are only being charged for the data processed by queries you run, hence this model is a true pay-per-use model , but thats not the case with SQL server

You can read more about the serverless benefits here

Please do let me know how it goes .
Thanks
Himanshu

-------------------------------------------------------------------------------------------------------------------------

• Please don't forget to click on or upvote button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how
• Want a reminder to come back and check responses? Here is how to subscribe to a notification
• If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators