The job history does not record the results of the query in the SP.

Nice to hear from you again.

Thanks. 🙂

You might be right on that. I'd use this to support my creation of creating a custom trigger. Thanks again.

Thanks for staying with me on this. I thot there was way i could avoid using triggers.

When I limit the DB condition to have only one database in the list, it works. But it wont let me list more than one database

Dit what you suggested. Created the multipart condition and a DB condition that has all the databases, in the target box i choose the DB condition but i get the...

I was able to delete the Enforce dbo objectset from [msdb].[dbo].[syspolicy_object_sets_internal]. When i tried creating the policy again i got this error: Object Set 'Enforce dbo Schema_objectset does not support...

I create a condition on the database facet which has 3 database names. I also create another condition on the Multipart naming and choose the @SchemaName = 'dbo'. I use...

Disregard my last reply. IT WORKED!! I had to enable the policy and after that it worked.

Thank you guys for helping out.

I am still able to create a stored procedure with a schema other than dbo after creating a policy that uses the 'Multipart Name' facet and "@Schema = 'dbo'".

So I used the schema facet and selected the @owner = 'dbo' in the expression box. When i tested it by creating a Stored procedure, it created my windows login...

Can you help me out with how to use PBM to enforce the use of schema qualified object

Yes, i meant Database users based on Windows group.

Thank you