Andy

(1) Use a WHERE clause

(2) SELECT 'KILL ' + CAST(session_id AS varchar(4))....

Be very careful with (2) - you may find yourself killing stuff that should be allowed to live if...

Try this for a start... it's amazing what you can find with a simple search!

http://support.microsoft.com/kb/259733

John

Probably not. You could try DENY CONTROL TO db_owner (that may not be the correct syntax), but that may not work because CONTROL is implicitly granted to db_owner. ...

Well, the requestor would say that, wouldn't he? If I were you, I would tell him that he's getting EXECUTE permission on all stored procedures, and nothing else that...

Does the account actually need all those permissions? Why don't you remove it from db_owner and just give it the permissions it needs?

John

Usually it's the one that would be easier to roll back - that's if DEADLOCK_PRIORITY is the same for each. Search the internet for "deadlock victim" for more information.

John

You could change the owner to sa or some other login.

John

I've never had to use it before, but I think you do it through the setup utility. You'll probably need the installation media. I imagine if you use...

MG Chowdary (6/22/2011)

---

created database role deny_read

added all users/groups to that role

Deny select on test_table to public

(all user are denied read perms on test_table as of now)

now,

revoke select on...

I believe that this error occurs when someone has changed the password on their Windows login but still has a connection to SQL Server from before the change.

John

You certainly won't be able to use a CTE, since it only lives as long as the batch that creates it. If you can find some way in SSIS...

Bhuvnesh

Looks like you've left a "=" or a "LIKE" or some such out of your WHERE clause.

John

Steve

You just need to use a PARTITION BY clause in your ROW_NUMBER function.

John

Jordon

One of the problems of using the GUI is that it throws up unexpected things like this. Try scripting the view out and editing the actual T-SQL.

John

Brandie, a full backup doesn't break the log chain, although a lost or corrupted log backup certainly would.

John