Re: Difficult qualified name problem
From: Stamey (Stamey@REMOVEThisAndTheDot.Farther.com)
Date: 11/27/02
- Next message: Vishal Parkar: "Re:Linked Server Error.."
- Previous message: Alvin Zhao[MS]: "RE: adding users to db fixed roles"
- In reply to: Daniel Pratt: "Re: Difficult qualified name problem"
- Next in thread: Stamey: "Re: Difficult qualified name problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Stamey" <Stamey@REMOVEThisAndTheDot.Farther.com> Date: Tue, 26 Nov 2002 23:59:56 -0500
OK, I'll check it out some more and get back to you.
My address: Stamey AT removethis Farther.com
Chris
"Daniel Pratt" <kolREMOVETHISkata_is@hotmail.com> wrote in message
news:eVuyPRXlCHA.2116@tkmsftngp07...
> Hi Chris,
>
> "Stamey" <Stamey@REMOVEThisAndTheDot.Farther.com> wrote in message
> news:#kt19dQlCHA.1464@tkmsftngp07...
> > What version of SQL Server are you using? I tried this on SQL 2000
before
> I
> > posted the reply and it seemed to work fine. I just tried it on 7.0 (the
> 200
> > box isn't available right now) and it did not work, giving the results
you
> > describe.
> > There is another way, by modifying a System stored procedure or two, if
> you
> > want to do that.
> >
> > Chris
>
> We are running SQL Server 2000, as well. If I do the following...
>
> 1. Log in as "sa"
> 2. Create the MakeTable procedure (now owned by "dbo").
> 3. Grant EXEC permission to testuser
> 4. Log in as "testuser"
> 5. Execute the MakeTable procedure.
>
> ...the result is a new table in the database, TestTable, which is
owned
> by "testuser", which is a problem for reasons I've mentioned previously.
>
> Regards,
> Dan
>
>
- Next message: Vishal Parkar: "Re:Linked Server Error.."
- Previous message: Alvin Zhao[MS]: "RE: adding users to db fixed roles"
- In reply to: Daniel Pratt: "Re: Difficult qualified name problem"
- Next in thread: Stamey: "Re: Difficult qualified name problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|