[google-cloud-sql-discuss] Re: MAXDOP gets reset back to default

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 

On Thursday, February 10, 2022 at 11:32:13 AM UTC+1 daria.a...@fitogram.pro wrote:

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

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/b3325bd0-c73d-4835-8d3c-32357723591an%40googlegroups.com.