In my CustomerLoad database, I don't want table names to have spaces in them so I'm going to set up a policy using the table facet to let me know if any tables are created with spaces in their names. So first of all I'll right-click on the table facet and go New Condition and give the condition a name. 

In the expression, I want to evaluate the name field or attribute of the table, so I'll select name from the drop-down, and then for the operator, I will select not like, and for the value I'll just specify the space between two % symbols. It's important that your value is enclosed in quotes.

Now I'll go up to policies under Policy Management and right-click and select New Policy. I'll give that policy a name and then from the check condition drop-down, I'll select the condition No space in table name that I just defined. Because it's a table facet, it's already checked against every table, but I also get to specify which database I want this policy to be run against.

So essentially, I am defining another condition here. So I'll set the database name equal to CustomerLoad. Having done that, I can now manually evaluate the policy by right-clicking and selecting evaluate from the context menu. And I can see that the Customer Item table with a space has been highlighted in the results.

So if I go and drop that table and then re-evaluate, I can see that it's all successful. The table facet doesn't allow for On change evaluations and we can see that by going into the properties and in the evaluation mode there is only on demand and on schedule.

So now I'm going to set up a policy to make sure that stored procedures when they are created with the prefix USP. Because the stored procedure facet does allow on change evaluation, I will be able to prevent, in real-time, users from creating stored procedures that do not conform to my naming policy. It's the same process as with the table name policy.

I'll create a new condition under the stored procedure facet, specify the name field, and use the like operator to compare with my value of USP_%. So go back to Policy Management and create a new policy, giving it a name and selecting the stored procedure prefix check condition.

Next, I'll specify on change prevent as my evaluation mode and again set the target database as CustomerLoad, not forgetting to enable the policy.

Now, let's try that out in real-time by creating a stored procedure that doesn't conform to my naming policy. Sure enough, we have an error there saying that the stored procedure doesn't meet the policy condition of name like USP_ and if I change that to usp_Customer_Item_Get then that will be successfully created.