No recent changes that I know of. We've stopped all non sql server processing and we don't allow reporting to run off the publisher.

We've had replication up and running from 2000 to 2005 for a while but now I also need to set it up the other way around. Every now and...

I agree with locking down these environments. Thanks for the advice guys.

Just to clarify, the issue only applies to my dev, qa and uat environments, not production.

Option 2 is my backup plan. However, I was interested in implementing option 1...

Just to clarify, this issue only applies to Dev,QA, and UAT environments, not production.

Option 2 is my backup plan. I would have like to go with option 1 if...

I've got the DDL trigger protecting schema changes but what about data changes? Aside of creating an instead of trigger on each table, how else can I restrict the...

Creating a new database would involve going back and making changes to 100+ servers which cannot be done at this time. This particular db exists on all servers which is...

I could but I am trying to stay away from splitting the database into 2 dbs because it will complicate maintenance especially in production.

Ok, so I was able to create a DDL trigger to prevent schema changes to the 225 tables. That works well but I no longer want to give them...

I like that option. How do I capture the name of the table involved in the DDL operation?

It seems to me the only way to do this...

Can you elaborate on how creating a schema and denying access to these objects would still allow them to create/alter any other objects under the dbo schema.

Lynn

I thought so. Thanks.