Network design VS Database Administration

A database administrator (DBA) is a person responsible for the design, implementation, maintenance and repair of an organization’s database. They are also known by the titles Database Coordinator or Database Programmer, and is closely related to the Database Analyst, Database Modeler, Programmer Analyst, and Systems Manager. The role includes the development and design of database strategies, monitoring and improving database performance and capacity, and planning for future expansion requirements. They may also plan, co-ordinate and implement security measures to safeguard the database.[2] Employing organizations may require that a database administrator have a certification or degree for database systems (for example, the Microsoft Certified Database Administrator).
20110113-database.jpg
Personal Characteristics/Skills:[3]
1. Strong organizational skills
2. Strong logical and analytical thinker
3. Ability to concentrate and pay close attention to detail
4. Strong written and verbal communication skills
5. Willing to pursue education throughout your career
Database administrator’s activities can be listed as below:[4][5][6]
1. Transferring Data
2. Replicating Data
3. Maintaining database and ensuring its availability to users
4. Controlling privileges and permissions to database users
5. Monitoring database performance
6. Database backup and recovery
7. Database security

20110113-network.jpg
A network planning methodology
A traditional network planning methodology involves five layers of planning, namely:
• business planning
• long-term and medium-term network planning
• short-term network planning
• IT asset sourcing
• operations and maintenance.[1]
Each of these layers incorporates plans for different time horizons, i.e. the business planning layer determines the planning that the operator must perform to ensure that the network will perform as required for its intended life-span. The Operations and Maintenance layer, however, examines how the network will run on a day-to-day basis.
The network planning process begins with the acquisition of external information. This includes:
• forecasts of how the new network/service will operate;
• the economic information concerning costs; and
• the technical details of the network’s capabilities.[1][2]
It should be borne in mind that planning a new network/service involves implementing the new system across the first four layers of the OSI Reference Model.[1] This means that even before the network planning process begins, choices must be made, involving protocols and transmission technologies.[1][2]
Once the initial decisions have been made, the network planning process involves three main steps:
• Topological design: This stage involves determining where to place the components and how to connect them. The (topological) optimisation methods that can be used in this stage come from an area of mathematics called Graph Theory. These methods involve determining the costs of transmission and the cost of switching, and thereby determining the optimum connection matrix and location of switches and concentrators.[1]
• Network-synthesis: This stage involves determining the size of the components used, subject to performance criteria such as the Grade of Service (GoS). The method used is known as “Nonlinear Optimisation”, and involves determining the topology, required GoS, cost of transmission, etc., and using this information to calculate a routing plan, and the size of the components.[1]
• Network realization: This stage involves determining how to meet capacity requirements, and ensure reliability within the network. The method used is known as “Multicommodity Flow Optimisation”, and involves determining all information relating to demand, costs and reliability, and then using this information to calculate an actual physical circuit plan.[1]
These steps are interrelated and are therefore performed iteratively, and in parallel with one another. The planning process is highly complex, meaning that at each iteration, an analyst must increase his planning horizons, and in so doing, he must generate plans for the various layers outlined above.[1][2]
The role of forecasting
During the process of Network Planning and Design, it is necessary to estimate the expected traffic intensity and thus the traffic load that the network must support.[1] If a network of a similar nature already exists, then it may be possible to take traffic measurements of such a network and use that data to calculate the exact traffic load [2]. However, as is more likely in most instances, if there are no similar networks to be found, then the network planner must use telecommunications forecasting methods to estimate the expected traffic intensity.[1]
The forecasting process involves several steps as follows:[1]
• Definition of problem;
• Data acquisition;
• Choice of forecasting method;
• Analysis/Forecasting;
• Documentation and analysis of results.

Network planning and design is an iterative process, encompassing topological design, network-synthesis, and network-realization, and is aimed at ensuring that a new network or service meets the needs of the subscriber and operator.[1] The process can be tailored according to each new network or service.[2]

Dimensioning
The purpose of dimensioning a new network/service is to determine the minimum capacity requirements that will still allow the Teletraffic Grade of Service (GoS) requirements to be met.[1][2] To do this, dimensioning involves planning for peak-hour traffic, i.e. that hour during the day during which traffic intensity is at its peak.[1]
The dimensioning process involves determining the network’s topology, routing plan, traffic matrix, and GoS requirements, and using this information to determine the maximum call handling capacity of the switches, and the maximum number of channels required between the switches.[1]. This process requires a complex model that simulates the behavior of the network equipment and routing protocols.
A dimensioning rule is that the planner must ensure that the traffic load should never approach a load of 100 percent.[1] To calculate the correct dimensioning to comply with the above rule, the planner must take on-going measurements of the network’s traffic, and continuously maintain and upgrade resources to meet the changing requirements.[1][2]. Another reason for “overprovisioning” is to make sure that traffic can be rerouted in case a failure occurs in the network.
Because of the complexity of network dimensioning, this is typically done using specialized software tools. Whereas researchers typically develop custom software to study a particular problem, network operators typically make use of commercial network planning software (e.g. OPNET Technologies, SevOne, WANDL, VPISystems, Cariden, Aria Networks). However, there is one notable open source network planning software available by the name of TOTEM named after TOolbox for Traffic Engineering Methods.
Traffic engineering
Comparing to network engineering, which adds resources such as links, routers and switches into the network, traffic engineering targets to change traffic paths on the existing network to alleviate traffic congestion or accommodate more traffic demand.
This technology is critical when the cost of network expansion is prohibitively high and network load is not optimally balanced. The first part provides financial motivation for traffic engineering while the second part grants the possibility of deploying this technology.
The available technologies for traffic engineering include MPLS and ATM for current Internet backbone. For example, MPLS allows carriers to provision LSPs with dynamic or explicit routes. The dynamic routes is controlled by CSPF while the explicit routes are optimized in an offline tool or through a path computation element which is under study by IETF. Fast reroute has been implemented by major vendors, such as Cisco and Juniper Networks, to provide localized resilient capability for MPLS networks. End-to-end protection is an alternative resilient approach. It provisions a backup route for each primary route. Pre-planning enough bandwidth for these backup routes is one of the active topic for survivable network design.
Provisioning a large number of LSPs also brought up a scalability problem. Various solutions have been proposed and it is still an active topic under study.

Share

Short URL: http://komputerbutut.com/?p=75

Posted by on Jan 13 2011. Filed under Internet. You can follow any responses to this entry through the RSS 2.0. You can leave a response or trackback to this entry

2 Comments for “Network design VS Database Administration”

  1. These tiny components can damage easily if a large amount of current passes through
    them. They also sustain enough space between the elements to allow warm dissipation. Check out
    for great tips for choosing a manufacturer of printed circuit boards, right now.

  2. Excellent post however , I was wanting to know if you could
    write a litte more on this topic? I’d be very grateful if you
    could elaborate a little bit further. Bless you!

Leave a Reply

Featured Links

Search Archive

Search by Date
Search by Category
Search with Google

halaman

Blog Vitals

Blog Stats
Google Page Rank
1,832,194

Photo Gallery

120x600 ad code [Inner pages]
Top Posts Overall
  • No posts viewed yet.
Popular Search Termsstraight cable, jenis antena wireless, straight through, antena wireless, jenis antena wifi, remote client warnet, macam-macam antena wireless, 568a vs 568b, cable straight, macam-macam antena wifi
Log in | Designed by Komputerbutut themes - sumber Backlinks - Seo Primitif - Seo Ranger - IT BSA - Copas SEO