Policy Based Management: Changes are not fully rolled back after a failure.

I’ve started using Policy Based Management to control some of the settings within my SQL instances. One of the policies I’ve created controls the Max Memory setting. I ran into a little problem using the apply function.

The Problem

Consider the following memory configuration:

Min Memory Setting: 2048 MB

Max Memory Setting: 2048 MB

Then you apply a policy which reduces the Max Memory Setting to 1023 MB, you would receive an error:

This would suggest the change has not been made effective. However: the only part that failed was the RECONFIGURE statement. The setting itself has been changed. Next time the reconfigure statement is ran, it will fail. One of those moments is during a SP installation.

The solution

Create a policy which sets the Min Memory setting to be lower than the Max Memory setting.

Advertisements

About sqlsmurf
MS SQL Administrator

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: