July 12, 2008 at 2:51 am
Hello All,
I have Windows Small Business Server 2003 Premium Edition running SQL Server 2005 WorkGroup Edition with an active instance. I need to provide access to a new database to a developer to work on and I am not sure how to go about this. The developer will need access "ONLY" to this database and nothing else. Any ideas on how to go about this?
Thank you.
J
July 12, 2008 at 6:14 am
Create a login for the developer (preferably using windows authentication) Do not assign the login to any of the fixed server roles. Map that login to a database and grant it just what permissions it needs in the DB.
You can create the login and map to a DB via management studio's create new login dialog.
What does the developer need to be able to do in the DB.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 12, 2008 at 6:48 am
Thanx for your response. I am not too conversant with SQL (and may need some hand holding step-by-step instructions) but I have basically done the following;
Run SQL Server Management Studio (as Administrator) and connect to your SQL
Server, using Windows Authentication. If 'Object Explorer' is not visible,
open it from the 'View' menu item.
Click on 'Security' and right-click on 'Logins'. Click 'New Login'. Click
the 'Search' button next to the 'Login Name'. Make sure the location is set
to the domain name (See: 'From this location') Add the user account you want
to have access to the database and click 'OK'. You just created a Login
object for user. Click 'OK' again.
Now right click on the 'Databases' folder and select 'New Database'. Give
the database a name, next to the 'Owner' field click the button, and type
the login name you just created. If you don't type the domain name a window
will show up with the name that matches what you typed. Click the checkbox
next to the login and then 'OK'. Under 'Database Files' you'll see the name
of the the database and the log. To the right, under 'Path', is the place
on the hard drive where you specify where you want the files stored. You
can change that path if you like. Click 'OK'.
This is the quick and dirty way. There are other options that need to be
set, but the developer should be able to set them since s/he is the db
owner.
In summary, I created a database as described above and permitted the developer access to it. On the network firewall, I have also forwarded TCP port 1433 and UDP port 1434 to the SQL server on the network. Please let me know what else I need to do and how I need to test connectivity to it remotely on the LAN and WAN.
Thanx again.
July 12, 2008 at 6:50 am
Pretty much, however you have made the developer the owner of that DB. That means he can do absolutely anything with it, including increasing the size of the data or log files, doing backups, even dropping the database.
Are you sure you're happy with that?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 12, 2008 at 5:42 pm
Well, as long as the developer does not have access to anything else on the server he can do as he wishes with the database provided to him to accomplish his primary development goal. How do I test connectivity on/with this database before making it available to him as fully functional?
Thanx for the response.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply