Deprecated: Function set_magic_quotes_runtime() is deprecated in /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php on line 1505 Call Stack: 0.0026 466740 1. {main}() /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:0 0.0043 539364 2. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:25 0.0045 540652 3. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php:20 0.0056 614964 4. vB_Registry->vB_Registry() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php:43 0.0057 615620 5. vB_Input_Cleaner->vB_Input_Cleaner() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php:2337
Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /archive/global.php on line 26

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3113

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265
SQL Server role members [Archive] - MCSE
PDA

View Full Version : SQL Server role members

Jakob Bengtsson
04-11-04, 09:50 PM
something
Hi,

I've created roles in a database. Each role has members consisting of various NT security groups.

When I try to determine if someone is a member of a role, it seems that only explicit members are returned as valid.

I'm using the IS_MEMBER scalar function, but the result is not as I had hoped.

Example:
In RoleA I have NTGroupA. If I log on to the database as a member of NTGroupA and execute IS_MEMBER('RoleA') it returns zero, when in fact I am a member of the role implicitly.

Is there some way of resolving this? Any help would be appreciated.

Regards,
Jakob
Jasper Smith
04-11-04, 09:50 PM
something
There's probably a simpler way I'm blanking on but you can get the
permission path for a user using xp_logininfo e.g.

use master
go

create procedure sp_isinrole
(
@role sysname,
@result bit OUTPUT -- 1 = yes,0 = no
)
as
set nocount on
declare @group sysname
declare @u sysname ; set @u = SUSER_SNAME()
create table #info
(
account sysname,
type sysname,
privilege sysname,
mappedlogin sysname,
path sysname
)
insert #info
exec master..xp_logininfo @u
select @group = path from #info

if exists (
select 1 from sysmembers where memberuid =
(select uid from sysusers s
join master.dbo.sysxlogins x on s.sid=x.sid
where x.name = @group)
and groupuid = (select uid from sysusers where name = @role))
set @result = 1
else
set @result = 0

drop table #info
return
go
grant exec on sp_isinrole to public

-- test logged as member of nt group and in relavent database
use <dbname>
go
declare @result bit
exec sp_isinrole 'db_datareader',@result OUTPUT
select @result

Unfortunately the insert exec negates the use of a UDF (without using a
loopback linked server)

--
HTH

Jasper Smith (SQL Server MVP)

I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org


"Jakob Bengtsson" <j.bengtsson@email.dk> wrote in message
news:D57B05BD-E9D0-43F4-9FCA-DD220C55714D@microsoft.com...
> Hi,
>
> I've created roles in a database. Each role has members consisting of
various NT security groups.
>
> When I try to determine if someone is a member of a role, it seems that
only explicit members are returned as valid.
>
> I'm using the IS_MEMBER scalar function, but the result is not as I had
hoped.
>
> Example:
> In RoleA I have NTGroupA. If I log on to the database as a member of
NTGroupA and execute IS_MEMBER('RoleA') it returns zero, when in fact I am a
member of the role implicitly.
>
> Is there some way of resolving this? Any help would be appreciated.
>
> Regards,
> Jakob
Jakob Bengtsson
04-11-04, 09:51 PM
something
Hi Jasper,

Thanks for replying.

When I try your solution I get a result of zero each time, so it doesn't seem to work for me.

I have tried testing it with all roles in the database, also roles for which my membership can be discovered using the IS_MEMBER function -- all return zero.

But, thanks for helping out.

Jakob
Baisong Wei[MSFT]
04-11-04, 09:51 PM
something
Hi Jakob,

From you information, you have an NT group and this group is a login of the
SQL Server and is belong to a role of one database. Is_member () do not
reflect this information.

I want to know if you have the latest Service Pack for both you windows and
SQL Server. How many roles have you already have in your database? Another
thing is, if you reboot you computer, could it work?

You could download the latest Service Pack from
http://support.microsoft.com/default.aspx?scid=fh;en-us;sp

Looking forward to your reply.

Thanks.

Best regards

Baisong Wei
Microsoft Online Support
----------------------------------------------------
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
Jakob Bengtsson
04-15-04, 06:16 AM
something
Hi Baisong,

Thanks for replying.

You understand the problem correctly.

I'm running the developer edition of SQL Server with SP3 on my Windows 2003 development machine. No service packs are installed for Win2003 but I stay current with the Automatic Updates feature.

I have rebooted the machine, but this does not help.

In this database I have four roles, apart from the built-in roles.

Best regards,
Jakob
Baisong Wei[MSFT]
04-16-04, 03:53 AM
something
Hi Jakob,

Thanks for the update. Well, I take a test on my machine and did not
re-produce the problem. Could you follow my steps and try again, I log in
my computer as system administrator:
1) I create some windows account, my machine name is BAIWEI:
BAIWEI\test1
BAIWEI\test2
BAIWEI\test3
2) I create a windows group BAIWEI\testgroup, and add the above three
account in this windows group
3) In the SQL Enterprise Manager, I only add this windows group
BAIWEI\testgroup as a SQL Server login
4) Then, in SQL Enterprise Manager, in the pubs database, I add this SQL
login BAIWEI\testgroup as the database user.
5) Then in the pubs database, I created a database role 'groupmember' and
only add this database user 'BAIWEI\testgroup' in this role, all the other
settings are default.
6) I log off and again log in my computer with account 'test1'.
7) In the Query Analyzer, I run the following T-SQL:
select is_member('groupmember')
I got 1.

As IS_MEMBER() Indicates whether the current user is a member of the
specified Microsoft Windows NT group or Microsoft SQL Server role. I run
select is_member('BAIWEI\testgroup')
I got 1too.

Could you take the exact above steps and check if you got the same results?
Looking forward to your reply.

Best regards

Baisong Wei
Microsoft Online Support
----------------------------------------------------
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
Jakob Bengtsson
04-16-04, 03:53 AM
something
Hi Baisong,

Thanks for your continued help.

I have tried the steps outlined by you.

My result differs, however. The name of my computer is Apollo34

IS_MEMBER('groupmember') returns 0

IS_MEMBER('Apollo34\testgroup') returns 1

Best regards,
Jakob Bengtsson


"Baisong Wei[MSFT]" <v-baiwei@online.microsoft.com> wrote in message
news:1AcEpa3IEHA.2432@cpmsftngxa06.phx.gbl...
> Hi Jakob,
>
> Thanks for the update. Well, I take a test on my machine and did not
> re-produce the problem. Could you follow my steps and try again, I log in
> my computer as system administrator:
> 1) I create some windows account, my machine name is BAIWEI:
> BAIWEI\test1
> BAIWEI\test2
> BAIWEI\test3
> 2) I create a windows group BAIWEI\testgroup, and add the above three
> account in this windows group
> 3) In the SQL Enterprise Manager, I only add this windows group
> BAIWEI\testgroup as a SQL Server login
> 4) Then, in SQL Enterprise Manager, in the pubs database, I add this SQL
> login BAIWEI\testgroup as the database user.
> 5) Then in the pubs database, I created a database role 'groupmember' and
> only add this database user 'BAIWEI\testgroup' in this role, all the other
> settings are default.
> 6) I log off and again log in my computer with account 'test1'.
> 7) In the Query Analyzer, I run the following T-SQL:
> select is_member('groupmember')
> I got 1.
>
> As IS_MEMBER() Indicates whether the current user is a member of the
> specified Microsoft Windows NT group or Microsoft SQL Server role. I run
> select is_member('BAIWEI\testgroup')
> I got 1too.
>
> Could you take the exact above steps and check if you got the same
results?
> Looking forward to your reply.
>
> Best regards
>
> Baisong Wei
> Microsoft Online Support
> ----------------------------------------------------
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only. Thanks.
>
>
Baisong Wei[MSFT]
04-16-04, 06:02 PM
something
Hi Jakob,

Thanks for you update. One thing I should confirm is that, the user you
login into your system and run the is_member() should NOT be the system
administrator of the SQL Server, that is, it should not belong to the
sysadmin server role.

Also, could you please provide the following information:
use master
go
select * from syslogins
select * from sysxlogins
use pubs
go
select * from sysmembers
select * from sysusers
exec sp_helprolemember
exec sp_helpuser

Looking forward to your reply. Thanks.


Best regards

Baisong Wei
Microsoft Online Support
----------------------------------------------------
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
Jakob Bengtsson
04-19-04, 03:17 AM
something
Hi Baisong,

The user I log in with is as previously specified by you (test1, test2 or
test3, all members of testgroup role in PUBS), none of which are in the SA
role. I have double-checked just to make sure, and none of the users are in
the SA role.

The results of the SQL statements in your previous post are attached as a
zipped text file (results.zip).

Thanks for your help.
Jakob


begin 666 results.zip
M4$L#!!0````(`*M.DS"QB=O.D X``,9W`0`+````<F5S=6QT<RYT>'3M75VH
M)$<5KF4CA)C :I#X$,+%J.P&=JGI^5\%F5]9W=R-=UV?(LG]V[MW]_[MG7MS
M=U&?5A%!E'U1U >)XF->U!!!5)*0IXA!$!\,YL$($O.@@O@@DO6<T]-WNOIV
M37?-5O?L=!T^NF?Z=%6=GIJJ.E^?JCY]Y[V!6!<K8HYA'0.Q)Q9AVX=O<V)9
M[(I5.EZ%^O8_DTJ8'/MBYU!+]MH6X=<MYZ#'QY[8AFT9?N%^C'P=]FKZ`:3$
M*UP5&W!V$[:]87H\BDKGZ'\:0-D;( F?VX)2-G/X??<N5L22X[6 +6D`.(!6
MMNODN+D!-; EUJ!_+,+>Q7:P`K]Z2]R$FMB&&EB'[[[\"K4-?RQ<I5;BR]?A
MVQ:,(-&>$\C7H"5MTXBMRM%NK,*Y(/T`=&+Y*S0B;87DJZ!Q'U+B.'532>&7
M\!SMH_(]TJF6MT/7$EQ_^-P*7=>U(_IQ3!C9MNW#ZUVB$?1H^E&MN3J2/"0>
M$*<9F6!NS%'6<%';M.3N@&N :X!KP'1\F)9\DCSZLDQSF,K=@<^ZI+@!6PFV
M*FQQJ,)9]5Q3E$4/MIKP1$4T1!^V)NS;<%2'#=-[L+5 AI*VZ$"NQF'^)#98
M#)247^K1+Z] O4NHN=-PM@%2K,NS<%RE?4.<@6]E0%+924BK#?_!>F)I24BK
MS<YODU.2MZ 5+X@+XBG8SHMSXJ)X&N[6-@"NW*^UH0X6H!8N)J8L*N;%)?CO
MSR>F*R[0`_,,>7O6R!,\$%<2\Q0+4B,O69)+2_))\NCDYCET\G&C:%Y\I P;
MY@KRQU]IT3">CV!]8!J/K#7N2_!YAFK;/D,HDC8Y)7E<3VH-C\[#O@PU\%%-
MWF)@DV87]I09`;? ?(3YB-3(;?$.T_0Z^21Y='+S'#IYNE$T/V92$<Q,\)?[
MUML;[C%-">RVI'T5<(8DX7R3(<H5O"%7J)&>1H@KV/!=Y/O;="5D+8_K4U?%
M$FSQZ8L'9B;,3)B92(V<F4D:N7X4G92-M,">8:D=^"P-40,NTH?//ISO`U=!
MAE(&F4=LI3+4X2/^.HN&='Z2*MEJG.% QG &N%O-@B^AR-KDE.11-H_\/EA_
MMTY6>C>R3J]H8#;";(39B-3(F8VDD9N,HOGQD[9 RQ7DC[_RHD'/3RJT]J(F
M\%_TK7>=++D'-KPA;*_T&*>M:84QI-5FY[?)*<F/]JP]>M;@Z%,0107S$^8G
MS$^D1F[*3VSQ$)U\DCPZN7D.G3S-*!KPDA98$(_F6_ID0;J0HTE,HTE2/(]<
MI$U\P_?%XUQ-$V0]8"?Q5^ ZDOPFHS6AZ%4Z2PP.?0M5"[:[R-KDE.2+XCJ,
MR$>?K70'S$N.B3^=N'/Y/Q^_\L7V:U_]\^W'.\_^]C??]0Y^.O^S%]Y\]-9G
M?O1/^?VO_.WXRR\^_\O_O3O_8%)ILPCF)5(CSYIGF,HGR:.3F^?0R: .C:,!!
M.L L.L \ZF0Q\/X5UXHTX+,$$N0CN/J@2WRC*4K$:= [XI'/HZO1YCJ2.$A5
M!&L[RN0_*-/\!K)!NVL[BJ9-3DF^1#$B5@_CT+@'KH%CXN75DRN/[?[^[<=?
M?^.)^=/?V]M[K/*1^3?O'-PX<?R##RS<OO_=JX^\[Q>R6OO)K=-O)Y4VBV .
M(C5RYB!IY*,Q1)V9\6W(452/G/%">SGFBMW&9.M8);&[I+*3D%Y;S<+_EUZ;
MC=\FIR1OBTOBG#@O/@_[^;$SG@--";,.]H#PS RS#ZF1F\[ F+(5T_3CSIG*
MS7/HY":C:,!/*C0;@W,N. >#\S%]V%=@CS,T7?A>HIF9'GE+FN0U:9!E0Q_)
MW5N<8F(\/_%75V":LX=^A"JMKK"]EJ-HVN24Y MB%)7W2>A%UYRSTU@#&(5S
ME^)]%GD-KP['Q,\[%\[?]]>KY]YY^*4?//O6\<9+#_WC8Q?>^]T3:_>W;[U3
M_L!GO=W[OO"MTM>^_NCM_RXFE3:+8'XB-7)3_I"U?)(\.KEY#IT\?A0->TKB
M\S$F1QP3D<.5%+CWUWF6(NL\:S0_EE1V$L:MWB@/UW#40%N%9N222DM"OK]-
M3DF.<;'CS[@"]I0<$Y\[\9WC/W[PAX]\Z-^O_NN;2V_\\>%7%C[UE^>__?Y;
M.Z_OOO7BUJ___N$7OO&K5_[PZI<_\:5/)I4VBV F(C7RK)F(:?GCSIG*S7/H
MY#B*(N_ [>301N+:U0,X&HA3`E>37 ;X]SIXYW/J,/V WFD0O+>(WV"4%6X(
M]1U&-P[?\9,'3QQI\Q+3WCU<?1O%"/QN&X;_/I?1>,IO^UDG:[,#5@B]^,A\
M=X;2*^(Z/6NQ=RC%M^IL@,U2I='WO7 T]JP0K=E\:[K(VNY%< TPHJV VT1\
M#9A)T6*I:T$FB7!@&@_2S3=GU"+'48]MMN^72*O-SKLS^*T2O,**@1Z\L$>#
M/:G22#H=Z^3J>Q0JRK$NBEXV;QO(5UNZZ-A)I<PRV#HQHO-+;)VDD71:ULG-
M6/IZZY1]Q/FH=<HVFC['F6?KQ&#K%(4TDMJQ3N:Q2]V,K9[NWBF;".3Y:C.)
MF)M4UFR"K1.#K5,4TD@Z+>OD8F3M<?-.V<>?3JO-3FSM-/%2D\J8;;!U8K!U
MBD(:2>.M$\=7S@+1%=_Y1B'.5QO''AZQ/#F,=X$LK0^]J$9[C[XUH+:[4/\>
M]!KTKV)LC*[ >*$>677TEDOB?6V*G5&G.<(ZK2S"'MJ#SS*4CKG:D*M#'+ "
M$HPTVA<^!\3>6J=8I'62= 3&Y:C25;6IY Z5A.5)[K\6P=9)A322QELGCKR;
M!9*M4Y;Q:?/5QC%9P]:I0_5<)?M?(QZ'=@)97XGF:SVR&&WJ=YYHD97PR$HU
MJ0_6AWG*9,=\J]0EJ](G2U4GGX6D?[9$_W2+M#5)VB#+4R-;5*?_O4TV#%-7
MR?ZUJ#^726?/PK_/"*#.&+-UDD;2<9X]CLQJ%U[$/J5=%2&%C?BEZ;79B,UJ
M$F\OJ:S9!'OV&'SO%(4TDL9;)X[+F07&W3ME'[TR7VT<LS)\[X1]J4)W/K@>
MJ$/_0X]Z68OZ3V_H@6B3EZ)-/:E+7K8R^2S:=,_3)3\ZKGVMT%U3C_QQ>*]5
MH_,-NK/">Z >^3K*Q#TJY/OSZ%X-]5;)G]BCLPVZ9\+>Z_M ^E16'A%.7(':
MD]@Z22.I_MXIOG3&Y/"??QTAWXB&^49KY#B&8>M4%?[<;)/L3ID8G"2+@!P/
MK4-U:+?*)&G -YR90D]?E^P%>OX\:@]ELDL>,<0&S2SY?KHZE=@>>@Q[-*]4
MH\\>,<P2,<>N:)#]ZU)YW:'..NW;-)M5YGDGB^![)Q722.K'#@[+V".1%4HT
MIS,Z3NMKP[D_N]8I>VW<BK@&&-%QE]N$C)7&WPN5E BSF"9MA%F,!+HIELA?
MLS^,ASA:*QQ(HI']=%&5_)1QUX@^IS+Y+#!%59.B0B/OZ+=X!K\DN%8?:CQ7
MCGG*L8.S`K;/#?)_)J5D%!?+]+:BQ>&HY'\FY9D<.#:OY*9MD?SZP?C*T9,9
MR!'"]@2]",_1&[NVG5S7[3JNT)B $;47821<)FN(]A"]2AO0)M8BZ_U1OD7K
M+55>%LBC3ZL%<F1SX9G%==)S'72H9];)YXM>K462KQQ)'UCM</H=@"H?']&:
M8[!R#60%KEE&WJU@FMKRU<VX-\%M@C&"[O^???G1N43U"#VO2\1?EQ6Y.V#_
M?U;PUX+(Q'2,(B/->B\_@JB]]5YY:9/*$8\D#&X3C##DC,CU;\#UY]F#.?6C
M9: O]AF:.=]R[ED,']S'LP(S2$9Z3N=9:2OY:E/'71Y)&,P@&6'(&9&G8Y#5
MF#)\!AF>SW<M<A_W\:S #)*1-Z?+5QLS2$844CGB-N$VY(S(TS'(6DP9/H,<
MT-,Z^V(7F..>N.D4B^0^GA6803),.)V-]R;GJXT9)",*J1QQFW ;<D;DZ1AD
M/:8,GT&N`#:<XHTC<!_/"LP@&7ESNGRU,8-D1"&5(VX3;D/.B#P=@VS&E.$S
M2/^Y]&OT1/DV;*N%?TOW"-S'LP(S2$;>G"Y?;<P@&5%(Y8C;A-N0,R)/PR";
MP]QJ&8$/<I$B2OI1WE:<>J:&^WA68 ;),.%T90MOP\A7&S-(1A12.>(VX3;D
MC,C3,<A23!DJ@SP8KH1D!LFX>S"#9.3-Z?+5Q@R2$854CKA-N TY(_)T#-*+
M*2-@D!AG_Z:3ODCNXUF!&20C;TZ7KS9FD(PHI'+$;<)MR!F1IV.0Y9@RXAFD
M2[Y([N-9@1DDPX3352VTE7RU,8-D1"&5(VX3;D/.B#R9058.;;E:QNB=C.%W
MAL>75DQP'\\*S" 9`:>K$)O#?6G(Z9K$Z1JPQ[M;Y'05"\^VY*N-&20C"M7:
M<IMP&W)&Y.,9I*?(U*,U8(\827Q/4T+QP3PG*W#-,M)[!>V\9W"<-IRW1FW(
M(.M66J9:`K,%!K<)1A@Z9J9G;';D]LKW?9!AF<H@<19[6Y/;#?@\1U?CC,G!
M-<LP89!U"YPN7VUJ"<P6&-PF&&$4@T%6%5E-.6J)I\0%:N,7X Z](IZFU8_H
MDQS-;\>7710$/$?2RJ@X5.&L>JX%UJDE.H &G/-1$VW1A\\^G.^+'FP-J-$V
MS9WUX5/"49 _Z9J*@< 'Z8.9I)M(GE<N0<\X`U(;G"Y9FS^+7:9G:9)*2X)4
MCI@M,'@6FQ&&*8,TE<O,Y<@@<3L)UU !";+"`S@:B%-PM"@N`_"-AL@;5T 6
MI.^*);$`:3= 'E]VT?%D:%WH/-34IG,U$:Z!B^(<M(FD'(QTP!YVVG',):8H
M.K@&LH+?P_RG1-'>;3FWNM\'SS &_B%L#_S,!_L+I^$O''%PG/]/R\ OT;O&
M;7#/3Q_^MVG*.@]IU^C-E&E2CT,7\EZ&??M(2<%O\SDE<\NL8)-GFK$5L]3C
MH"]I;LP1PQ[\=F3/=IC987MZ-V$4&L3&!U'GV*9E(^RQ-3/F.X!Z22HQ'?0U
MK'K 5%9FZSF*'2AI26R [5I.3&O3MZLO25WO%\RH!1;^_U!+`0(4"Q0````(
M`*M.DS"QB=O.D X``,9W`0`+````````````( ````````!R97-U;'1S+G1X
7=%!+!08``````0`!`#D```"Y#@``````
`
end
Baisong Wei[MSFT]
04-20-04, 03:15 AM
something
Hi Jakob,

Thanks for your information. I check the results from you, it is no problem
from a SQL Server side. What I mean is that it is same as mine. So, the
last thing I need to check is out of the SQL Server. If a windows account
is the windows system administrator, it will belong to a system
administrator login, which is Buildin\Administrators. The
Buildin\Administrators login is also belong to a SQL Server server role
'Sysadmin'. So, could you delete the Buildin\Administrators and try again.
Actually, it is recommended to delete it for security concern. Please refer
to the 'SQL Server Logins, Users, and Roles' part in the following article:
Checklist: Securing Your Database Server
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/ht
ml/CL_SecDBSe.asp

Then try again. Waiting for your results. Thanks.

Best regards

Baisong Wei
Microsoft Online Support
----------------------------------------------------
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
Jakob Bengtsson
04-20-04, 07:11 AM
something
Hi Baisong,

Thanks for your help. Deleting the Builtin\Administrators helped.

IS_MEMBER() now returns the correct value in all cases I've tested so far.

Thanks again and best regards,
Jakob
vBulletin v3.6.2, Copyright ©2000-2010, Jelsoft Enterprises Ltd.