SQL Server Agent enabled but not able to start/stop it to run DB jobs
we installed MS Sql Server 2022 standard edition DB at on-prem K8S cluster using helm chart (taken from: https://artifacthub.io/packages/helm/mssql/mssql/1.1.2 ) and added following configuration to helm chart(templates/primary/statefulset.yaml) to enable SQL Server agent name: MSSQL_AGENT_ENABLED value: "true" and was trying also to trigger from sa user: EXEC sp_configure 'show advanced options', 1; RECONFIGURE; EXEC sp_configure 'Agent XPs', 1; RECONFIGURE; however, although SQL server agent is enabled, i'm still not able to start or stop it when login as sa user, what helm chart configuration or sql statement i can execute to start it? for example:
Availability Groups in Big Data Clusters. Two or more replicas in the same node?
Recently we have observed a couple of occurrences where 2 or more AG replicas in a Big Data Cluster deployment are being executed within the same node. In this post we will discuss this scenario, its cause and how can we avoid it.
