how can a user who is in a role assign his role to another user?

I create a role(eg. HighOperators), and add user 'ABC01' into it. 'ABC01'
is not a member of the sysadmin fixed server role or the db_owner fixed data
base role or the db_securityadmin fixed database role, can he assign his ro
le to another user?
In SQL Server Books Online, it says " Role owners can execute sp_addrolememb
er to add a member to any SQL Server role they own". but I don't know how to
set or get the a role's Owner.The only way I know to set the role owner is when you create
the role, specify the owner of the role in the second
argument for sp_addrole.
In terms of retrieving the owner, I don't remember there
being a direct way. I think it may be that the altuid in
sysusers is the uid for the owner of the role.
-Sue
On Tue, 27 Apr 2004 05:31:04 -0700, samuelzhu
<anonymous@.discussions.microsoft.com> wrote:

>I create a role(eg. HighOperators), and add user 'ABC01' into it. 'ABC01'
is not a member of the sysadmin fixed server role or the db_owner fixed dat
abase role or the db_securityadmin fixed database role, can he assign his r
ole to another user?
>In SQL Server Books Online, it says " Role owners can execute sp_addrolemember to a
dd a member to any SQL Server role they own". but I don't know how to set or get the
a role's Owner.

hotfix for: KB816939 (PRB: File Growth Value for TempDB is Not Per

Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent When
Changed From Fixed Increments to Percentage):
Does anyone know if microsoft has included a fix for this in sp4, or has a
hotfix for this bug?
We tried the workaround listed in the KB, but it did not work...
Link:
http://support.microsoft.com/defaul...n-us;816939#kb4Can you give more info regarding how the work around did not work?
As far as I know the fix did not make it into SP4...
It is fixed in SQL 2005 though.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:FF219273-52D1-42C0-8CE5-35CDF27E01BD@.microsoft.com...
> Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent
When
> Changed From Fixed Increments to Percentage):
> Does anyone know if microsoft has included a fix for this in sp4, or has a
> hotfix for this bug?
> We tried the workaround listed in the KB, but it did not work...
> Link:
> http://support.microsoft.com/defaul...n-us;816939#kb4

hotfix for: KB816939 (PRB: File Growth Value for TempDB is Not Per

Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent When
Changed From Fixed Increments to Percentage):
Does anyone know if microsoft has included a fix for this in sp4, or has a
hotfix for this bug?
We tried the workaround listed in the KB, but it did not work...
Link:
http://support.microsoft.com/default...-us;816939#kb4
Can you give more info regarding how the work around did not work?
As far as I know the fix did not make it into SP4...
It is fixed in SQL 2005 though.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:FF219273-52D1-42C0-8CE5-35CDF27E01BD@.microsoft.com...
> Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent
When
> Changed From Fixed Increments to Percentage):
> Does anyone know if microsoft has included a fix for this in sp4, or has a
> hotfix for this bug?
> We tried the workaround listed in the KB, but it did not work...
> Link:
> http://support.microsoft.com/default...-us;816939#kb4

hotfix for: KB816939 (PRB: File Growth Value for TempDB is Not Per

Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent When
Changed From Fixed Increments to Percentage):
Does anyone know if microsoft has included a fix for this in sp4, or has a
hotfix for this bug?
We tried the workaround listed in the KB, but it did not work...
Link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816939#kb4Can you give more info regarding how the work around did not work?
As far as I know the fix did not make it into SP4...
It is fixed in SQL 2005 though.
--
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:FF219273-52D1-42C0-8CE5-35CDF27E01BD@.microsoft.com...
> Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent
When
> Changed From Fixed Increments to Percentage):
> Does anyone know if microsoft has included a fix for this in sp4, or has a
> hotfix for this bug?
> We tried the workaround listed in the KB, but it did not work...
> Link:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;816939#kb4

Hotfix fixed my SQL Server

I have the same problem. Did you get a fix?
Thanks!
~ Troy

>--Original Message--
>I've applied "Hotfix 8.00.0859", which I downloaded from
the Microsoft site,
>and now I get the "Invalid cursor state" error described
here
>http://support.microsoft.com/?kbid=831997
>The article says there is another hotfix that fixes what
the previous hotfix
>screwed up, and one should contact "Microsoft Product
Support Services" to
>get the new hotfix, and give a hyperlink to support where
you can pay to
>call MS, etc, which I don't really intend to do.
>Anyone knows of a better way to get this new hotfix, have
a link to it
>maybe? I've downloaded the previous one, don't understand
why this one is so
>special.
>Thanks.
>
>.
>> I have the same problem. Did you get a fix?
Did you read the rest of the thread you replied to?|||The direct link to the fix that fixed it for me (thanks to Aaron) is
http://support.microsoft.com/?kbid=838166
"Troy Anderson" <tanderso@.sonoma-county.org> wrote in message
news:322801c46385$3df4f380$3a01280a@.phx.gbl...[vbcol=seagreen]
> I have the same problem. Did you get a fix?
> Thanks!
> ~ Troy
>
> the Microsoft site,
> here
> the previous hotfix
> Support Services" to
> you can pay to
> a link to it
> why this one is so

Hotfix fixed my SQL Server

I've applied "Hotfix 8.00.0859", which I downloaded from the Microsoft site,
and now I get the "Invalid cursor state" error described here
http://support.microsoft.com/?kbid=831997
The article says there is another hotfix that fixes what the previous hotfix
screwed up, and one should contact "Microsoft Product Support Services" to
get the new hotfix, and give a hyperlink to support where you can pay to
call MS, etc, which I don't really intend to do.
Anyone knows of a better way to get this new hotfix, have a link to it
maybe? I've downloaded the previous one, don't understand why this one is so
special.
Thanks.> give a hyperlink to support where you can pay to
> call MS, etc, which I don't really intend to do.
I suppose you've never done this before. If it's a bug in the product, and
they provide you with a fix, you are not charged for the call. In any
case...

> maybe? I've downloaded the previous one, don't understand why this one is
> so special.
Most hotfixes are not freely available because, as the article always
states, it is only intended to fix the specific problem for those sites that
are having the problem (e.g., not everyone and their brother). The reason
the hotfixes aren't handed out to everyone is because they are not fully
regression tested, and could possibly introduce other problems (e.g.
"Invalid Cursor State").
In your case, there is a newer hotfix that is publicly available. See the
end of http://www.aspfaq.com/2515
I would *STRONGLY* recommend, in the future, that you do not apply hotfixes
just because they are available to download from the Microsoft web site.
http://www.aspfaq.com/
(Reverse address to reply.)|||Aaron, thanks for the link, I am going to give the hotfix a shot.
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
Actually I've been programming with SQL Server for 10 years now and this was
my first hotfix ever, applied last Sunday after fighting a Report Server
install for about six hours, and someone that had the problem gave the
advice. In the end it was something else, but after six hours you don't ask
questions any more, I was ready for a total SQL Server re-install.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> I suppose you've never done this before. If it's a bug in the product,
and
> they provide you with a fix, you are not charged for the call. In any
> case...
>
is[vbcol=seagreen]
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||Hi Aaron,
The link you gave me to the hotfix fixed the problem, thanks.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> I suppose you've never done this before. If it's a bug in the product,
and
> they provide you with a fix, you are not charged for the call. In any
> case...
>
is[vbcol=seagreen]
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>

Hotfix fixed my SQL Server

I've applied "Hotfix 8.00.0859", which I downloaded from the Microsoft site,
and now I get the "Invalid cursor state" error described here
http://support.microsoft.com/?kbid=831997
The article says there is another hotfix that fixes what the previous hotfix
screwed up, and one should contact "Microsoft Product Support Services" to
get the new hotfix, and give a hyperlink to support where you can pay to
call MS, etc, which I don't really intend to do.
Anyone knows of a better way to get this new hotfix, have a link to it
maybe? I've downloaded the previous one, don't understand why this one is so
special.
Thanks.
> give a hyperlink to support where you can pay to
> call MS, etc, which I don't really intend to do.
I suppose you've never done this before. If it's a bug in the product, and
they provide you with a fix, you are not charged for the call. In any
case...

> maybe? I've downloaded the previous one, don't understand why this one is
> so special.
Most hotfixes are not freely available because, as the article always
states, it is only intended to fix the specific problem for those sites that
are having the problem (e.g., not everyone and their brother). The reason
the hotfixes aren't handed out to everyone is because they are not fully
regression tested, and could possibly introduce other problems (e.g.
"Invalid Cursor State").
In your case, there is a newer hotfix that is publicly available. See the
end of http://www.aspfaq.com/2515
I would *STRONGLY* recommend, in the future, that you do not apply hotfixes
just because they are available to download from the Microsoft web site.
http://www.aspfaq.com/
(Reverse address to reply.)
|||Aaron, thanks for the link, I am going to give the hotfix a shot.
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
Actually I've been programming with SQL Server for 10 years now and this was
my first hotfix ever, applied last Sunday after fighting a Report Server
install for about six hours, and someone that had the problem gave the
advice. In the end it was something else, but after six hours you don't ask
questions any more, I was ready for a total SQL Server re-install.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> I suppose you've never done this before. If it's a bug in the product,
and[vbcol=seagreen]
> they provide you with a fix, you are not charged for the call. In any
> case...
is
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
|||Hi Aaron,
The link you gave me to the hotfix fixed the problem, thanks.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> I suppose you've never done this before. If it's a bug in the product,
and[vbcol=seagreen]
> they provide you with a fix, you are not charged for the call. In any
> case...
is
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>

Hotfix fixed my SQL Server

I have the same problem. Did you get a fix?
Thanks!
~ Troy

>--Original Message--
>I've applied "Hotfix 8.00.0859", which I downloaded from
the Microsoft site,
>and now I get the "Invalid cursor state" error described
here
>http://support.microsoft.com/?kbid=831997
>The article says there is another hotfix that fixes what
the previous hotfix
>screwed up, and one should contact "Microsoft Product
Support Services" to
>get the new hotfix, and give a hyperlink to support where
you can pay to
>call MS, etc, which I don't really intend to do.
>Anyone knows of a better way to get this new hotfix, have
a link to it
>maybe? I've downloaded the previous one, don't understand
why this one is so
>special.
>Thanks.
>
>.
>
> I have the same problem. Did you get a fix?
Did you read the rest of the thread you replied to?
|||The direct link to the fix that fixed it for me (thanks to Aaron) is
http://support.microsoft.com/?kbid=838166
"Troy Anderson" <tanderso@.sonoma-county.org> wrote in message
news:322801c46385$3df4f380$3a01280a@.phx.gbl...[vbcol=seagreen]
> I have the same problem. Did you get a fix?
> Thanks!
> ~ Troy
> the Microsoft site,
> here
> the previous hotfix
> Support Services" to
> you can pay to
> a link to it
> why this one is so

Hotfix fixed my SQL Server

I've applied "Hotfix 8.00.0859", which I downloaded from the Microsoft site,
and now I get the "Invalid cursor state" error described here
http://support.microsoft.com/?kbid=831997
The article says there is another hotfix that fixes what the previous hotfix
screwed up, and one should contact "Microsoft Product Support Services" to
get the new hotfix, and give a hyperlink to support where you can pay to
call MS, etc, which I don't really intend to do.
Anyone knows of a better way to get this new hotfix, have a link to it
maybe? I've downloaded the previous one, don't understand why this one is so
special.
Thanks.> give a hyperlink to support where you can pay to
> call MS, etc, which I don't really intend to do.
I suppose you've never done this before. If it's a bug in the product, and
they provide you with a fix, you are not charged for the call. In any
case...
> maybe? I've downloaded the previous one, don't understand why this one is
> so special.
Most hotfixes are not freely available because, as the article always
states, it is only intended to fix the specific problem for those sites that
are having the problem (e.g., not everyone and their brother). The reason
the hotfixes aren't handed out to everyone is because they are not fully
regression tested, and could possibly introduce other problems (e.g.
"Invalid Cursor State").
In your case, there is a newer hotfix that is publicly available. See the
end of http://www.aspfaq.com/2515
I would *STRONGLY* recommend, in the future, that you do not apply hotfixes
just because they are available to download from the Microsoft web site.
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Aaron, thanks for the link, I am going to give the hotfix a shot.
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
Actually I've been programming with SQL Server for 10 years now and this was
my first hotfix ever, applied last Sunday after fighting a Report Server
install for about six hours, and someone that had the problem gave the
advice. In the end it was something else, but after six hours you don't ask
questions any more, I was ready for a total SQL Server re-install.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> > give a hyperlink to support where you can pay to
> > call MS, etc, which I don't really intend to do.
> I suppose you've never done this before. If it's a bug in the product,
and
> they provide you with a fix, you are not charged for the call. In any
> case...
> > maybe? I've downloaded the previous one, don't understand why this one
is
> > so special.
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||Hi Aaron,
The link you gave me to the hotfix fixed the problem, thanks.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> > give a hyperlink to support where you can pay to
> > call MS, etc, which I don't really intend to do.
> I suppose you've never done this before. If it's a bug in the product,
and
> they provide you with a fix, you are not charged for the call. In any
> case...
> > maybe? I've downloaded the previous one, don't understand why this one
is
> > so special.
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||I have the same problem. Did you get a fix?
Thanks!
~ Troy
>--Original Message--
>I've applied "Hotfix 8.00.0859", which I downloaded from
the Microsoft site,
>and now I get the "Invalid cursor state" error described
here
>http://support.microsoft.com/?kbid=831997
>The article says there is another hotfix that fixes what
the previous hotfix
>screwed up, and one should contact "Microsoft Product
Support Services" to
>get the new hotfix, and give a hyperlink to support where
you can pay to
>call MS, etc, which I don't really intend to do.
>Anyone knows of a better way to get this new hotfix, have
a link to it
>maybe? I've downloaded the previous one, don't understand
why this one is so
>special.
>Thanks.
>
>.
>|||> I have the same problem. Did you get a fix?
Did you read the rest of the thread you replied to?|||The direct link to the fix that fixed it for me (thanks to Aaron) is
http://support.microsoft.com/?kbid=838166
"Troy Anderson" <tanderso@.sonoma-county.org> wrote in message
news:322801c46385$3df4f380$3a01280a@.phx.gbl...
> I have the same problem. Did you get a fix?
> Thanks!
> ~ Troy
> >--Original Message--
> >I've applied "Hotfix 8.00.0859", which I downloaded from
> the Microsoft site,
> >and now I get the "Invalid cursor state" error described
> here
> >http://support.microsoft.com/?kbid=831997
> >
> >The article says there is another hotfix that fixes what
> the previous hotfix
> >screwed up, and one should contact "Microsoft Product
> Support Services" to
> >get the new hotfix, and give a hyperlink to support where
> you can pay to
> >call MS, etc, which I don't really intend to do.
> >Anyone knows of a better way to get this new hotfix, have
> a link to it
> >maybe? I've downloaded the previous one, don't understand
> why this one is so
> >special.
> >
> >Thanks.
> >
> >
> >.
> >