Beware Group Policy
Group Policy is a useful tool in the armoury of systems administrators, but make sure they are aware of the impact on your SQL Servers.I have been affected twice by this in the last 2 months. In both cases the servers were working fine, until one day when several had problems at the same time.
- Cluster nodes were unable to join an existing cluster, or to form a new cluster. Investigation showed that the cluster service account had been removed from the local Administrators group on each node.
- SQL Servers started registering errors on restart due to the SQL Server service account no longer having "Lock Pages In Memory" right.
To prevent this, there are 2 things you should do:
- Make sure that your infrastructure system administrators are aware of the impact their changes can have, and try to work more closely with them in the future;
- If you have a documented change management process (if not, why not?) and there is not currently a DBA on the Change Advisory Board, make sure you are invited as soon as possible.
Not found what you're looking for?
Use this search box. It is tuned for SQL Server searches. Try it and see!Do you have a question about SQL Server? Would you like to answer a question?
Go to the SQL FAQ to get started.
