Category Archives: Architecture Of Data Warehousing

Top 5 Interview Tips for Junior DBA Position

Top 5 Interview Tips for Junior DBA Position

Are you thinking of becoming a Junior DBA also known as a database administrator? Like many other professions, getting your first job as a Junior DBA is not at all easy. You can check out on the Internet for open positions related to this job profile. You would come to know that even if it is a junior position, a relevant experience of a few years in SQL is asked for by most of them.

It is a fact that a majority of SQL DBA’s begin their career path in an alternative field, which means that they have accidentally become DBA’s. Therefore, such people have to gain the required experience in their current role at job, so that they can work as a Junior DBA.

If one is really wishing to begin the career as a SQL DBA, or switch from their current position to this one, this fact would prove to be a heart breaking one. It would make you feel like a no win situation.

Well, there is no need to worry as SQL experience is not the only skill that is needed. Most of those who are the accidental ones, are often the self study types. Even if they appear to be more experienced than you, they have gained the SQL knowledge by the harder path. Therefore, an experienced DBA can easily to knowledge transfer to a fresher. This was all about the general picture today, as far as DBA is concerned.

Now, lets’ move on to the top interview tips for the position of Junior DBA’s:

1. Why do you wish to become a DBA?

Employers usually search for candidates, who know why they need to be a Database Administrator. There is no such thing as a perfect answer here yet you should have the capacity to show to the interviewer that your reasons are clear and have been thoroughly thought about.

2. Are you aware about the core responsibility of a Junior DBA?

This question is a must ask for the recruiters. If you are not yet aware, then do read it right now! This position is that of a DBA Prime Directive. As a data professional, your output is built on further.

3. Can You Debug and Solve Problems?

At the heart of being an excellent Database Administrator is a capacity and a drive to issue resolving. You should have the capacity to viably show your enthusiasm for issue resolving. Problem solving is not by any stretch of the imagination an aptitude that you can instruct however it can positively be enhanced and improved through practice.

You should have the capacity to show a decent level of problem solving to the employer.

Be set up for your interview whether it be up close and personal or via phone, with an entire host of examples that exhibit your capacity and flair to debug problems.

4. Have You Set Your Goals?

Make sure that you can give details of both your short (inside the following year) and long term (next five years) goals. This may interface into your Professional Development planning yet you may likewise wish to incorporate points of interest of your life goals. Again there is no set in answer here, as the goal is to exhibit that you are ground breaking and aggressive yet in the event that you need to quit fooling around about your objectives then you will need to ensure that they are SMART objectives.

5. Are You Aware about Database Backups?

In a perfect world you ought to get to grasps with the fundamentals of SQL Server backups, however as an exceptionally least you should know why they are essential and why they are vital.

These are some of the top and important tips for those aspirants who aspire to be in the position of a junior DBA in their career.

Don't be shellfish...Digg thisBuffer this pageEmail this to someoneShare on FacebookShare on Google+Pin on PinterestShare on StumbleUponShare on LinkedInTweet about this on TwitterPrint this pageShare on RedditShare on Tumblr

What Is The Purpose Of Data Warehousing Tuning?

What Is The Purpose Of Data Warehousing Tuning?

A data warehousing keeps changing and it is unforeseen what question the customer is going to write later on. Therefore it becomes more challenging to track a information factory program. In this section, we will talk about how to track the different factors of a information factory such as efficiency, information fill, concerns, etc.

data-warehousing-tuning

Difficulties in Data Warehouse Tuning

Tuning a information factory is a challenging process due to following reasons:

Data factory is dynamic; it never continues to be continuous.

It is hard to estimate what question the customer is going to write later on.

Business requirements change eventually.

Customers and their information keep changing.

The customer can change from one group to another.

The information put on the factory also changes eventually.

Note: It is very essential to have an extensive knowledge of information factory.

Performance Assessment

Here is a list of purpose actions of performance:

Average question reaction time

Check out rates

Time used per day query

Memory utilization per process

I/O throughput rates

Following are the indicates keep in mind.

It is necessary to specify the actions in service level contract (SLA).

It is of no use trying to track reaction time, if they are already better than those required.

You must have genuine objectives while making efficiency evaluation.

It is also essential that users have possible objectives.

To cover the complexness of it from the customer, aggregations and opinions should be used.

It is also possible that the customer can write a question you had not updated for.

Data Load Tuning

Data fill is a critical part of over night handling. Nothing else can run until information fill is finish. This is the access point into it.

Note: If there is a wait in shifting the information, or in appearance of information then the entire product is affected poorly. Therefore it is very essential to track the information fill first.

There are various techniques of adjusting information fill that are mentioned below:

The very common strategy is to place information using the SQL Part. In the process, normal assessments and restrictions need to be conducted. When the information is placed into the desk, the rule will run to check for enough area to place the information. If enough room is not available, then extra area may have to be assigned to these platforms. These assessments take the a chance to perform and are costly to CPU.

The second strategy is to avoid all these assessments and restrictions and place the information straight into the preformated prevents. These prevents are later written to the data source. It is quicker than the first strategy, but it can work only with whole prevents of information. This can lead to some area waste.

The third strategy is that while running the information into the desk that already contains the desk, we can maintain indices.

The 4th strategy says that to fill the information in platforms that already contain information, drop the indices & reproduce them when the information fill is finish. The choice between the third and the 4th strategy relies on how much information is already packed and how many indices need to be renewed. oracle course is always there for you to provide quality based training in Pune.

 

Don't be shellfish...Digg thisBuffer this pageEmail this to someoneShare on FacebookShare on Google+Pin on PinterestShare on StumbleUponShare on LinkedInTweet about this on TwitterPrint this pageShare on RedditShare on Tumblr

What Is The Architecture Of Data Warehousing?

What Is The Architecture Of Data Warehousing?

In this chapter, we will discuss the company research structure for the details factory style and structure of a details factory.

Business Analysis Framework

The company analyst get the details from the details manufacturing facilities to measure the performance and make critical adjustments in order to win over other company holders in the market. Having a details factory offers the following advantages:

Since a details factory can gather details quickly and efficiently, it can enhance company productivity.

A details factory provides us a regular opinion of customers and items, hence, it helps us manage customer relationship.

A details factory also helps in bringing down the costs by tracking trends, patterns over a long period in a regular and reliable manner.

To style an effective and efficient details factory, we need to understand and analyze the company needs and construct a company research structure. Each person has different opinions regarding the style and style of a details factory. These opinions are as follows:

The top-down perspective – This perspective allows the selection of relevant details needed for a details factory.

The databases perspective – This perspective presents the details being captured, saved, and managed by the functional program.

The details factory perspective – This perspective includes the fact platforms and dimension platforms. It represents the details saved inside the details factory.

The company question perspective – It is viewing details from the viewpoint of the end-user.

Three-Tier Data Warehouse Architecture

Generally a details manufacturing facilities adopts a three-tier structure. Following are the three tiers of the details factory structure.

Base Level – The end tier of the structure is the details factory data source server. It is the relational data source program. We use the back end resources and resources to feed details into the bottom tier. These back end resources and resources perform the Extract, Clean, Load, and refresh functions.

Middle Level – At the center tier, we have the OLAP Server that can be implemented in either of the following ways.

By Relational OLAP (ROLAP), which is an extended relational data source management program. The ROLAP maps the functions on multidimensional details to standard relational functions.

By Multidimensional OLAP (MOLAP) model, which directly implements the multidimensional details and processes.

Top-Tier – This tier is the front-end client part. This part holds the question resources and reporting resources, research resources and knowledge mining resources.

Data Warehouse Models

From the perspective of data factory structure, we have the following details factory models:

Exclusive Warehouse

Data mart

Enterprise Warehouse

Virtual Warehouse

The perspective over an functional details factory is known as an online factory. It is easy to build an online factory. Building an online factory requires excess capacity on functional data source servers. Our oracle training is always there for you to make your profession in this field.

Don't be shellfish...Digg thisBuffer this pageEmail this to someoneShare on FacebookShare on Google+Pin on PinterestShare on StumbleUponShare on LinkedInTweet about this on TwitterPrint this pageShare on RedditShare on Tumblr