- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
It is recommended to set 3625 (trace flag)
database flag to off
for GCP SQL Server instance.
Microsoft SQL trace flags are frequently used to diagnose performance issues or to debug stored procedures or complex computer systems, but they may also be recommended by Microsoft Support to address behavior that is negatively impacting a specific workload. All documented trace flags and those recommended by Microsoft Support are fully supported in a production environment when used as directed. 3625 (trace log)
limits the information returned to users who are not members of the sysadmin fixed server role, by masking the parameters of some error messages using ‘******’. Setting this in a Google Cloud flag for the instance allows for security through obscurity and prevents the disclosure of sensitive information. Hence, it is recommended to set this flag to off
globally to prevent the flag from being left on or turned on by bad actors. This recommendation is applicable to SQL Server database instances.
Changing flags on a database may cause it to be restarted. The best time to do this is when there is low usage.
3625
from the drop-down menu, and set its value to off
.Configure the 3625
database flag for every GCP SQL Server database instance using the below command.
gcloud sql instances patch <INSTANCE_NAME> --database-flags "3625=off"
This command will overwrite all database flags previously set. To keep the flags previously set and add new ones, include the values for all flags you want set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).
Configuring the above flag restarts the GCP SQL Server instance.
Some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines.