« April 2010 | Main | July 2010 »
May 4, 2010
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
SQL Server 2008 Policy Management: Defining and Exporting your ‘Golden’ Database State
Policy Management under SQL Server 2008 allows you to define settings for the properties of target objects that control the behavior or characteristics of those objects. One such managed target is a database. Once defined, these polices can then be enforced across all SQL Instances in your enterprise.In this blog we’ll see how one can create a ‘golden’ copy of a production database with all of the properties set to specific agreed-upon values and then export the current state of this database as a policy. This is a very nice shortcut for creating policies perhaps based on a template and can be a real time saver. It’s like a having a way of saying “All production databases across our enterprise must look and behave like this database template. Also, if a production database is created without adhering to this policy we need to know!”
The Database Facet
Facets provide us with the properties that model the behavior or characteristics of a managed target. For a database, there are about 60 properties. Facets provide us with a single view of all properties which for the database facet include Name, Collation, Compatibility level, Auto Close, Encryption Enabled, Log and data File Location, etc. Interestingly, most literature dealing with Policy Management designates the feature's start-point in Management Studio as being Management --> Policy Management --> Policies. However, you are able to access the facet dialog from the database context menu by choosing the Facets menu item. (right click on a database and choose the facet menu option) The screen shot below displays the facet dialog for the MaketingLeads database and shows us what properties are exposed by this facet:
Notice there are numerous properties than can be fine-tuned . (Many of these same properties are exposed and can be changed from the Options Tab present under database properties window) Also, notice the Export Current State as Policy button in this screen snapshot. This is the specific feature that allows you to take a snapshot of the current state and save the behavorial characterstics under the protective umbrella of a single policy. The Export as Policy dialog box is captured below:
In conclusion, exporting the current state can be a quick and easy method for creating policies that monitor any changes from an original state. Consider including in your production database ‘golden copy’ conditions that enforce the well-known Microsoft Database Best Practices such as the Data and Log files must reside on different drives. Further, you may consider supplementing these with your own internal organization specific best practices. You may also consider creating other production templates that leverage other facets. For example -- a 'Production Lockdown' policy can be created that is based on settings made against properties exposed within the Surface Area facet.
Share:
Posted by Steve Mann at 10:47 AM | Comments (0)
Twitter 
LinkedIn 
YouTube