I didn't, unfortunately.  At one point, I had grand ideas of taking this to our MS TAM and letting him open an SRX for me, but ended up taking care...

A good reason?  Not really.  In our case, we're moving a legacy application up to SQL 2005, and we don't want to make any wholesale authentication changes until we stabilize...

Would db_owner or owning the database in question cover this role?  My user is in this scenario now for 2 separate database; still no luck...

Thanks!

Allan

This article should probably be revised to reflect the above?:

http://www.sqlservercentral.com/columnists/aGrinberg/thearrayinsqlserver2000.asp