November 12, 2008 at 8:24 am
Comments posted to this topic are about the item Extract User-Role Mapping
December 24, 2008 at 9:29 am
Versioning is too specific. You'll have to update this code everytime you apply a CU or SP. Why not just look at the first character? Show us how without the cursor, there must be a set-wise way to do this.
July 8, 2009 at 8:31 am
I receive this error:
Msg 213, Level 16, State 7, Line 2
Insert Error: Column name or number of supplied values does not match table definition.
This does not look well...
Greetz,
Hans Brouwer
July 9, 2009 at 6:58 pm
Hi Hans,
I am not getting any error, I have executed it & there is no
July 9, 2009 at 6:59 pm
Hi Hans,
I am not getting "Insert Error: Column name or number of supplied values does not match table definition." Its working fine.
Please try again & let me know if there it still give problem.
Thanks
Sudhir
July 9, 2009 at 7:27 pm
Hi Sigal,
Actually the only purpose to use cursor is to avoid DBO, SYS, INFORMATION_SCHEMA and Guest users, else we can directly execute sp_helpuser and it will return all user's role data.
To avoid cursor, while creating #tmpuser table, we can add another field with identity column and then run a while loop.
We have to run a loop to get roles of each user excluding system users.
your comments are appreciated.
Thanks
Sudhir
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy