when I right click properties on db2 I get Owner "Sa"

when I right click properties on db1 I get Owner "Sa"

is there somewhere else I should check?

-Francisco

quote:

---

Be aware, the user doesn't have to any rights to the tables or views in question. Simply being a user in...

quote:

---

With that said, if the user doesn't exist, I'd recommend setting up a user/role structure similar to what you have in...

I was hoping to avoid refering a view, but in any case wouldn't the view suffer the same problem since it's accessing objects from the other database?

... just tried it...

My setup is Sql Server 2000 w/ SP2, and I see the checkbox for cross db ownership chaining but it's grayed out.

I've checked that the user exists in both db's,...

No problems here, I am using OE tho.

-Francisco

I like the "break all his fingers" option. but I suppose this may not fly with his boss, although my boss would probably do it for me

Thank you that is a big help...this is the script I am gonna go with...

DELETE #CL_FINAL

FROM #CL_FINAL AS CL1 INNER JOIN (SELECT * FROM #CL_FINAL WHERE CorrectResponseID = 1)...

maybe my post is confusing.. let me reword it... hmm,

you see the statement above (the one w/ the delete) is somehow not taking into consideration the where clause below it....

I noticed that you are sending in the query as a dynamic SQL. It would be better to bite the bullet as you say, and go the SP route,...

would you be so kind as to post the number of channels / IO cards that you are using? We have a few Sql Server in the company some...

No I haven't because I wanted to use "Blat" instead of sql_mail... I don't want to send it via Exchange.

Maybe I'm overlooking something, but I thought I could somehow save...

This was the solution reply to my post on another list, I want to thank anyone who was trying to figure out an answer for me... but also wanted to...

thanks for the help.

So... it will be safe for me to revoke his table write access, w/o affecting his ability to write sprocs that write to the table.. (correct?)

-Francisco

This is the results of the 2nd Query using the IN clause... looking at both I think the IN is faster, but I've always thought that the INNER JOIN could...