I would create new roles, and double check what rights are granted them. Using db_reader/writer is a way to unintentionally allow access to tables.

Make sure that the instances are secured,...

It's yours. Write up a short article and submit it.

Peso,

Take it. I'll close this thread for now.

There's likely some caching going on. I'll have to get someone to flip through the .net code to get me the query.

Wayne has already tackled this. Thanks anyway.

Congrats to the Giants. I saw the 3 run shot in a restaurant last night and I knew then that the Rangers were done.

SSMS does a good job of administration. I'm not sure of a better one. In terms of performance, you have a few choices:

Red Gate is releasing SQL Monitor next week,...

Excellent, and thanks

Doh, my mistake here, and apologies Mike. I misread the first code you posted, thinking you were changin permissions for the sproc at compile time.

The AS DBO at the end...

No need to add it if you'll write it. I'm more looking for a place to keep track of holes that I find in the article base.

They do likely work because of ownership chaining, but that is not the same as including "AS DBO" in the proc. It might be OK for you today, but if...

We've talked about it, though it would require us to change some of the sending procedure to customize each newsletter. Otherwise when someone went to post a reply, answer the...

There is a difference.

If you use "as dbo" in the proc definition, then when the user executes it, it runs as if they were logged in as dbo, or an...

Default is "as the caller"

The permissions are set according to who executes it. The exception being that you might have ownership chaining enabled, so if the sproc owner owns a...

Back to SF. I have some confidence that those Texas boys will hit tonight.