Post reply

DBA Atributions

  • August 28, 2003 at 8:17 am

    #58725

    Hi,

    Recently I receive a request from may boss to write a job description paper for DataBase Administrator. Is anywhere on the Internet such a document or somebody could tell me what to write in that paper?

    Thanks.

  • August 28, 2003 at 8:21 am

    #471831

    Hi flooriin,

    quote:

    Recently I receive a request from may boss to write a job description paper for DataBase Administrator. Is anywhere on the Internet such a document or somebody could tell me what to write in that paper?

    it might help you to take a look at All Forums -> Job Posting. I think you'll find some examples there

    Cheers,

    Frank

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • August 29, 2003 at 3:30 am

    #471946

    Thanks Frank for your answer.

    I visit that part of the forum but are few job posting that didn't help me. I am relatively new to this forum and i don't know if was this sort of discussion around here ... i hope it was so I could inspire. Everyone talk about a DBA job, but what should do such a person. I think it is important to right about this.

    First of all, DBA person it's reponsable to maintain Sql Server up and running with possible few downtime or none.

    Second, it's responsable that server running at high performance. If this have not happend than he has to identify the bottlenecks and propose solution to the management staff.But this bottlenecks could be from hardware or from software. Hardware bottlenecks, i believe, are easy to diagnostic and to repair. But how about software that running on that machine and use databases under Sql Server instalation?! Here is the real deal.He have to deal with developer who write poor performing code, not make use of indexes etc.

    Third, he is responsable with disaster/recovery policy so any event not to conduct to the loss of data.

    I don't think he have to create indexes on tables, because from my point of view this is the developers job.They know the best what indexes they need. Let presume, we administer a databases with 500 stored procedures and 70 tables and views.To index that tables and views based on stored procedure i think it take you a lot of time. But, if developers when code see they need an indexes and propose to dba to create that index this is something else. The DBA know if it's need of that index or not based on other indexes on table/view.

    This is the main atributions of DBA from my point of view. If you have any comment please feel free to post it.

  • August 29, 2003 at 4:08 am

    #471947

    quote:

    I visit that part of the forum but are few job posting that didn't help me. I am relatively new to this forum and i don't know if was this sort of discussion around here ... i hope it was so I could inspire. Everyone talk about a DBA job, but what should do such a person. I think it is important to right about this.

    there might be only a 'few' job postings here, but in essence they should give you an impression on what 'normally' is expected from a DBA.

    quote:

    I don't think he have to create indexes on tables, because from my point of view this is the developers job.They know the best what indexes they need. Let presume, we administer a databases with 500 stored procedures and 70 tables and views.To index that tables and views based on stored procedure i think it take you a lot of time. But, if developers when code see they need an indexes and propose to dba to create that index this is something else. The DBA know if it's need of that index or not based on other indexes on table/view.

    UhOh, I would be careful with such statements!

    I bet this will give you many post from DBA's who do not follow your opinion on developers and their skills

    Curious, what happens!

    Cheers,

    Frank

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • August 29, 2003 at 7:10 am

    #471972

    Yes, no DBA will let developers handle indexes. Never happen. Laughing, especially, if you have him/her in the second qualification handling high performance. The database is either the DBA's or it is not. Indexing is a vital tool of the DBA.

    Yes, DBAs are responsible for disaster recovery.

    The DBA should also be responsible for designing/building databases and tables. They will also approve any stored procedures and views.

    The developers will NOT have sysadmin rights on the production database. The DBA will create users and roles, depending on your security model.

    They also have some networking needs and how much influence they have on that depends on your network gurus. DBA, unless it is a small shop, will probably not have network administrator access. The DBA should have local administrator access to the box with SQL Server.

    The DBA may help the developers with their queries, views and stored procedures. As I said earlier the DBA has approval on anything that happens on the production SQL Server. They should not care what developers do to the developer SQL Server.

    I assume that you have a developer/staging/production environment for developing the application/staging for testing/production for current version.

    I hope this helps.

    Bonne chance

    Dr. Peter Venkman: Generally you don't see that kind of behavior in a major appliance.

    Patrick

    Quand on parle du loup, on en voit la queue

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply