Skip to content

configure-sql-server-master-instance.md

Latest commit

 

History

History
65 lines (46 loc) · 2.53 KB

configure-sql-server-master-instance.md

File metadata and controls

65 lines (46 loc) · 2.53 KB
title Configure SQL Server master instance
titleSuffix Configure SQL Server master instance of Big Data Cluster
description Configure the master instance of a SQL Server Big Data Cluster
author MikeRayMSFT
ms.author mikeray
ms.reviewer mihaelab
ms.date 11/04/2019
ms.topic overview
ms.prod sql
ms.technology big-data-cluster

Configure master instance of [!INCLUDEbig-data-clusters-2019]

[!INCLUDEtsql-appliesto-ssver15-xxxx-xxxx-xxx]

Configure master instance of [!INCLUDEbig-data-clusters-2019].

Server configuration settings cannot be configured for SQL Server master instance at deployment time. This article describes a temporary workaround on how to configure settings like SQL Server edition, enable or disable SQL Server Agent, enable specific trace flags or enable/disable customer feedback.

To change any of these settings, follow these steps:

  1. Create a custom mssql-custom.conf file that includes targeted settings. The following example enables SQL Agent, telemetry, sets a PID for Enterprise Edition, and enables trace flag 1204.:

    [sqlagent]
enabled=true

[telemetry]
customerfeedback=true
userRequestedLocalAuditDirectory = /tmp/audit

[DEFAULT]
pid = Enterprise

[traceflag]
traceflag0 = 1204

  2. Copy mssql-custom.conf file to /var/opt/mssql in the mssql-server container in the master-0 pod. Replace <namespaceName> with the big data cluster name.

    kubectl cp mssql-custom.conf master-0:/var/opt/mssql/mssql-custom.conf -c mssql-server -n <namespaceName>

  3. Restart SQL Server instance. Replace <namespaceName> with the big data cluster name.

    kubectl exec -it master-0  -c mssql-server -n <namespaceName> -- /bin/bash
supervisorctl restart mssql-server
exit

Important

If SQL Server master instance is in an availability groups configuration, copy the mssql-custom.conf file in all the master pods. Note that each restart will cause a failover, so you must make sure you are timing this activity during downtime periods.

Known limitations

  • The steps above require Kubernetes cluster admin permissions
  • You cannot change the server collation for SQL Server master instance of the big data cluster post deployment.

Next steps

For more information about deploying SQL Server Big Data Clusters, see Get started with SQL Server Big Data Clusters.