September 29, 2009 at 6:56 am
Good Morning All,
I have been the administrator/developer on a one person single SQL install for a few years. Life has been good. My db's are now going to be assimilated into the larger corporate SQL environment.
I will still be the db owner of my db's but since I won't be the sysadmin I'm wondering what I might run into in terms of permissions?
Backups, sp's, imports/exports, functions etc...
I know my db's will now be backed up corporately....this is good...but I don't want to have to request a restore and then wait until the process completes and someone else has time....will I be able to take a nightly or even weekly backup myself and do a restore myself?
I am looking for any insight into what autonomies I am giving up.
Thank you,
Lonnie
September 29, 2009 at 7:28 am
Basically from now on you'll be free to perform config & maintenance but only for your own databases.
See also BOL ---> Permiossions of Fixed Database Roles & Permiossions of Fixed Server Roles
September 29, 2009 at 8:03 am
Depends on the company, being a database owner means nothing in some organisations. In those sort of companies. any work for those databases would be carried out by a member of the dba team.
If you are concerned about access and on-going support, I would ask who is responsible for the support and maintenance of your databases. If it is a member of the dba team, you can wave bye bye to what unrestricted access you had before.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
September 29, 2009 at 8:42 am
You shouldn't be worried about the time for a restore if it's not your responsibility. It might be a concern, and that is something you raise to your manager, but it isn't something you worry about. If the corporate company thinks that it's OK for a restore to take a day, and your work slowing, then all you can do is raise the issue.
In terms of permissions, the biggest issue I see is that traces, and potentially some DMVs might be an issue. So it can be harder to tune things. What I would aim for is a good test environment where you have all the permissions you need to do your job.
September 29, 2009 at 8:44 am
One more note. Be sure that you keep a document of issues. As you can't do something, note what it is, what impact is has on your job or the business, and polite suggestion on how to solve it. Send that to your manager, document what doesnt' work in the new system.
But try to make things works. Corporations sometimes seem to do silly things, and they might be. But they are the rules. Trying to work within them will make your life easier. Raise issues, document them, and then move on.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply