Data Administrator (DA) Data administrator is an organizational personnel working in the areas of information systems and computer science

that plans, organizes, describes and controls data resources(Malcher, 2011) Data resources are usually as stored in databases under a database management system or other software such as electronic spreadsheets. In many smaller organizations, data administrator performs occasionally. In the context of information systems development, data administrator ideally deals with system conception, ensuring there is a data dictionary to help maintain consistency, avoid redundancy, and model the database so as to make it logical and usable, by means of data modelling, including database normalization techniques. (Kuhn, 2010) In addition to the data management, work-flow process, and security tasks, the data administrator role can also perform data integration tasks. The following considerations apply to the Data Administrator role: Users who are assigned to the Data Administrator role have unrestricted access to all business data within their scope, even if they belong to a business role that has restricted settings. Assigning a member to the Data Administrator role does not guarantee explicit permissions to the staging and application database to perform all necessary tasks for data integration. For security reasons, work performed by Data Administrator should carefully review roles because of how users can browse databases. It's recommended that Data Administrator does not have full database permissions unless it is necessary. You must be a data administrator to add users to or remove users from the Data Administrator role. Before you can add a user to any Planning Server role, the user must first be added to Planning Server from the Users page.(Kreines, 1999) Database Administrator (DBA) A database administrator is a person responsible for the installation, configuration, upgrade, administration, monitoring and maintenance of physical databases.(Burleson, 1999)

The main role includes the design and development of database strategies, monitoring and improving database performance and capacity, and planning for future expansion requirements. He/she may also plan, co-ordinate and implement security measures to safeguard the database. A database administrator's responsibilities can include the following tasks:Task 1: Evaluate the Database Server Hardware:This evaluation should reveal the information such as; How many disk drives are available to the Oracle Products?, How many, if any, dedicated tape drives are available to Oracle products?, How much memory is available to the instances of Oracle Database you will run? Task 2: Install the Database Software; (Say Oracle) As the database administrator, you install the Oracle Database server software and any front-end tools and database applications that access the database. In some distributed processing installations, the database is controlled by a central computer (database server) and the database tools and applications are executed on remote computers (clients). In this case, you must also install the Oracle Net components necessary to connect the remote machines to the computer that executes Oracle Database. (Ault, 2003) Task 3: Plan the Database As the database administrator, you must plan: The logical storage structure of the database, The overall database design, A backup strategy for the database. Task 4: Create and Open the Database:After you complete the database design, you can create the database and open it for normal use. You can create a database at installation time, using the Database Configuration Assistant, or you can supply your own scripts for creating a database. Task 5: Back Up the Database:-

After you create the database structure, carry out the backup strategy you planned for the database. Create any additional redo log files, take the first full database backup (online or offline), and schedule future database backups at regular intervals. Logically structuring data:It can be defined as the conceptual blueprint of a software application, illustrating entities, relationships, rules, and processes (Ling, 2005). Once the relationships and dependencies amongst the various pieces of information have been determined, it is possible to arrange the data into a logical structure which can then be mapped into the storage objects supported by the database management system. In the case of relational databases the storage objects are tables which store data in rows and columns. Each table may represent an implementation of either a logical object or a relationship joining one or more instances of one or more logical objects. Relationships between tables may then be stored as links connecting child tables with parents. Since complex logical relationships are themselves tables they will probably have links to more than one parent. In an Object database the storage objects correspond directly to the objects used by the Object-oriented programming language used to write the applications that will manage and access the data. The relationships may be defined as attributes of the object classes involved or as methods that operate on the object classes. (Hernandez, 2003) Physical database design:The physical design of the database specifies the physical configuration of the database on the storage media. This includes detailed specification of data elements, data types, indexing options and other parameters residing in the DBMS data dictionary.(Roman, 2000) Application Programmers:By definition, He is an individual or groups of people who write/s application programs in a user organization. Most programmers are application programmers (Egbert, 2003). To others, An Applications Programmer is someone who works in many different programming languages to create the source code, which is responsible for creating small or large parts of a piece of software in concert with others. Applications Programming is the meat and potatoes of

programming, and requires a very creative mind, as well as one that can retain lots of information about the requirements of the software, the requirements of their team-mates and the code itself. (Brown, 1999) End Users (naive and sophisticated):Also known as the final or ultimate user of a computer system. The term end-user refers to the ultimate operator of a piece of software, but it is also a concept in software engineering, referring to an abstraction of that group of end-users of computers (i.e. the expected user or target-user) (Ruthman, 2011). The term end user usually implies an individual with a relatively low level of computer expertise. Unless you are a programmer or engineer, you are almost certainly an end user. According to (Sichel, 2005), Native end user; May be defined as end-users with one or more of the following characteristics: They use their first language for all human-computer interactions. They have minimal or no English knowledge. Their medium of education and instruction is in their native languages and socio-cultural environments. They may or may not posses computing skills. Native end-users referred to here include students (e.g., high schools, collages and universities etc.) and adults with general educational background although they may be complete novices with respect to computer use. Sophisticated End-users:According to (Jaeschke, 2000), sophisticated end users; Use full DBMS capabilities for implementing complex applications. Are usually Stand-alone users (personal databases).

References Ault, M.R., (2003). Oracle DBA made simple Oracle database administration techniques, Kittrell, N.C.: Rampant TechPress. Available [online] at: http://search.ebscohost.com/login.aspx? direct=true&scope=site&db=nlebk&db=nlabk&AN=98707 [Accessed February 18, 2012]. Brown, G.D. & Smith, S.A.M., (1999). MVS/VSAM for the application programmer, Boston: QED Pub. Group. Burleson, D.K., (1999). Oracle SAP administration, Sebastopol, CA: OReilly. Available [online] at: http://search.ebscohost.com/login.aspx? direct=true&scope=site&db=nlebk&db=nlabk&AN=24660 [Accessed February 18, 2012]. Egbert, P.K., (2003). UIPEX: design of the Application Programmer Interface. Urbana, Ill.: University of Illinois at Urbana-Champaign, Dept. of Computer Science. Hernandez, M.J., (2003). Database design for mere mortals: a hands-on guide to relational database design, Reading, Mass.: Addison-Wesley Developers Press. Jaeschke, G., (2008). Interactive programming by endusers: database access by forms, Heidelberg: IBM, Wissenschaftl. Zentrum. Kreines, D.C. & Laskey, B., (1999). Oracle database administration the essential reference, Kuhn, D., (2010). Pro Oracle database 11g administration, [S.l.]; New York: Apress; Distributed to the book trade worldwide by Springer Science+Business Media. Available at: http://proquest.safaribooksonline.com/?fpi=9781430229704 [Accessed February 18, 2012]. Ling, T.W., Lee, M.L. & Dobbie, G., (2005). Semistructured database design, New York: Springer. Available [online] at: http://search.ebscohost.com/login.aspx? direct=true&scope=site&db=nlebk&db=nlabk&AN=128284 [Accessed February 18, 2012]. Malcher, M., (2011). Oracle database administration for Microsoft SQL server DBAs, New York: Oracle Press/McGraw-Hill. Available [online] at: http://site.ebrary.com/id/10417019 [Accessed February 18, 2012]. Roman, S., (2000). Access database design & programming, Sebastopol, CA: OReilly. Available [online] at: http://search.ebscohost.com/login.aspx? direct=true&scope=site&db=nlebk&db=nlabk&AN=24409 [Accessed February 18, 2012]. Ruthman, F., (2011). Definition of collections, standards and procedures for restrospective digitisation. Available [online] at: http://igitur-archive.library.uu.nl/DARLIN/2005-0512200133/UUindex.html [Accessed February 18, 2012]. Sichel, B., (2005). Training Endusers on MathSci Disc. Special Libraries, 82(4), pp.282-87.