I can't find too much online about this, but I have seen one thread on here suggesting that whatI wnt to do is 'not advisable'.
Having said that, I am now intrigued, and want to explore the possibilities anyway.
So, I can see that there is a table dbo.policies, and I can see there is a stored procedure (dbo.policyadd).
I can see that the policy configuration is held in the 'policyXML' column and I can see that there are a number of different XML schemas depending on the PolicyType.
It seems that the stored procedure will create a new Identity Tag if the parameter is passed as blank or null, but it can't handle a blank CorrelationID.
This leads me to believe that there is more to creating a policy than simply adding it into the dbo.policies table.
Assuming that I could create the policies, I would then look to maintain an XML template for each policy type, and 'inject' that into the database when creating the server in the first place to provide simple and consistent builds.
Can someone please dissuade me from my quest by stating that it is simply not possible/supported? And can someone please also satisfy my curiosity by enlightening me as to what I am missing from the puzzle?
Thanks :)
This thread was automatically locked due to age.
