First, my background is mainly in ESRI ArcGIS Desktop. I have just started using Microsoft SQL Server 2005. I have created a new database using the ArcSDE Post-Install software. The database is an enterprise sde database. My problem is assigning users to the database and defining their roles within the database. As the database administrator I have full control. I can go back to the client machine and read/write, add new tables etc logging on as the user sde. The other users need permission to read and write. I added the user to the sql server and then added the user to the specific database users and set the user database role to db_datareader, db_datawriter and db_ddladmin. I also added the user as a user with full permissions to the sde schema properties. Although, when i go to the client machine, sign on as the user, the permissions are set to only allow viewing...i think it is using the default public server role.

 Can anyone help with assigning user database roles in an SDEdatabase using the Microsoft SQL Server Management Studio? I am unfamiliar, largely, with script. A lot of the help I have seen from Microsoft uses script and does not mention the link between sql and sde. Of course the ESRI help only says to contact your db admin for further help setting these permissions. I serve as both the GIS Analyst and the db admin in my current position.

 Any help would be greatly appreciated! Thanks BETH

Beth,

Could you script out the existing permissions? To do this, log in as the system admin, right-click the database, then choose Tasks -> Generate Scripts... From here, the wizard will guide you. Click next to get started. Select your database, then click next. On the next screen, set all the true/false values to false except "Script Object-Level Permissions" and "Script USE DATABASE". Then you will go through a series of steps (could be 8 or more depending on what objects your database contains) where you will simply choose "Select All (button on the bottom left) and then click next. FInally, you will arrive on a step for the Output Option. You can save it to a file or script to a new query window and then save that. Include this script in your reply and we can start looking at what is going on.

--Peter