MAXDOP gets reset back to default

[Daria Aleksich]

Since Cloud SQL Server is a managed database I can't set maximum degree of parallelism on an instance level, but am able override it by altering MAXDOP on a database level in DATABASE SCOPED CONFIGURATION. But for some reason, this MAXDOP gets very randomly reset back to default 0. As it affects the overall performance, I would like to understand how can this be fixed. Thank you in advance for all the suggestions

[goya]

There is an open feature request to set the MAXDOP on an instance level, you can check it in this link [1] and star it to give it more visibility. 

As a workaround, you could set the MAXDOP at a query level instead of database, so if the database setting changes the queries won't be impacted as they are now. 

[1]: https://issuetracker.google.com/218883128 

[2]: https://docs.microsoft.com/en-us/sql/t-sql/queries/hints-transact-sql-query?view=sql-server-ver15#maxdop-integer_value