August 29, 2005 at 3:48 pm
In SQL 2000, in the sysusers table, gid would be the uid of the role to which the user belongs.
In SQL 2005, in the sysusers table, gid is now 0 , though the user belongs a role.
Can someone give some input?
September 1, 2005 at 8:00 am
This was removed by the editor as SPAM
September 1, 2005 at 8:30 am
Sorry, no idea exactly what the reason for this is. It could of course be a bug. But remember that the old system tables of SQL Server 2000 are no longer there, the sysusers object (actually sys.sysusers) that you are using is a view that exists for backward compatibility.
September 1, 2005 at 10:54 am
The only reason for now, I want to use this view is that, our product still supports SQL 2000 and SQL 2005. I do not want to maintain 2 sets of scripts based on the SQL Server 2000. After we stop supporting SQL 2000, I want to modify the objects to use the new SQL 2005 system objects.
November 3, 2005 at 7:52 am
I too am looking for a way to support sysusers with SQL 2000 and SQL 2005. Any feedback would be appreciated.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply