QA Analyst/ Developer

CURRICULAM VITAE

M.Manik Prabhu

Phone no: 986-***-****

Email: ***********@*****.*** , ***********@*****.***

===============================================================

Career Objective: To work in a competitive environment to utilize my skills towards growth oriented and leading edge organization that recognizes and values individual contribution, which will provide opportunity for continuing growth and advancement.

Work Experience: 5.6 Yrs of Total Work Experience as Software Developer in

Teradata. Currently working With Bank Of America Corp.

Work Experience in Teradata Corp 4 Yrs. While working with Teradata Corp was working on TERADATA Product in supporting Team. Working Platform is in “C”, “C++” and “LINUX”. Worked With Teradata v2r5, v2r6, TD12, TD13, TD13.10, TD14 and TD14.10 Releases. Familiar with even DBA Concepts. Internal teradata training experience for new joinees.

Technical Experience:

Have been working for Teradata in supporting team for 4 Years . Have a good Knowledge of Teradata SQL. Worked on Syntaxer, Resolver and Optimizer phases of the Parser Section. Handled a wide range of problems in Resolver and Optimizer. Have a good understanding of the join processing, join planning, and query optimization and some of the complex features of Teradata. Have good debugging skills, handled debugging in both platforms Windows and Linux. Was Successful in handling performance problems and non reproducible problems.

• Well versed with Teradata RDBMS installation, upgrade/migration, and configuration, tuning and diagnosing performance issues.

• Good understandings of Teradata load/unload utilities like Tpump, FastLoad, MultiLoad and FastExport.

• Good knowledge of database monitoring, Teradata Tools & Utilities.

Working here as part of Teradata database sustenance engineering group.

I am responsible for providing critical support and resolving customer problems, in particular with issues related to Teradata Parser and Optimizer. I am a member of the level-4 support team providing 24/7 support to all the Teradata customers across the globe. I am in support and development of Teradata RDBMS since its V2R6 release.

The role requires an intricate understanding of the Teradata RDBMS Design and Architecture and its implementation across various releases and platforms, like UNIX, LINUX and W2K.

Professional Project Profile:

Projects handled in BOFA

Project: Enterprise Client Data Management.

Role: Analyst I Apps Programmer.

Duration: September 2010 to till data.

Team Size 4

Description: Integration of the Consumer, Commercial and Investment clients on to a single platform. Perform Data Quality and Analytics work on the ECDM Database.

Environment:

Teradata, Oracle, DB2, SAS Programming language. Teradata utilities.

Project: Teradata Database Engineering

Role: Grade 9 Team Member

Duration: October 2006 – September 2010.

Environment

Language: C/C++

Database: Teradata V2R5/V2R6/TD13/TD13/TD14.0

Tools: Teradata Visual Explain, BTEQ, TSET, Teradata SQL Assistant,

FastLoad, MultiLoad, Fast Export, Rational Clearcase, GDB

Debugger, X-term, GCC

O.S: Unix-MPRAS, WinXp, Suse Linux 9/10

Projects handled in Teradata

1. Project Name: Handling of Expressions which are forward referenced

Team Size: 1

Duration: 6 Months

Description: Forward reference of Expressions used to crash in the resolver phase, when the Expression is referred at a below nesting level than the level at which the Expression was referred. This project was developed to handle the above problem. The current problem has been handled in resolver module by checking If the Field is unresolved.Then resolve It and later call the routines which expected the resolved input.

2. Project Name: Early Error checking related to Aggregates

Team Size: 1

Duration: 6 Months

Description: Currently in Teradata the Error checking related to Aggregates with group by clause, Order by clause and having clause have been handled resolver, parser and optimizer modules. This project was developed to move more than 50% Error checking which has been done in parser and optimizer modules to query rewrite module. Along with the moving the error checking modules to the query rewrite phase handled 10+ issues related to Group by clause.

3. Project Name: Spooling /Folding views containing Deterministic and Non

Deterministic function.

Team Size: 1

Duration: 6 Months

Description: Views can have Deterministic and Non Deterministic functions and can be referred outside the view. Currently in Teradata views can either be folded or spooled. But in case of the Deterministic and Non Deterministic functions views was getting folded in few cases and spooled in few cases leading to ambiguous results. This project was developed to handle such cases.

4. Project Name: Re usage of Memory segments in optimizer and qrwmodules.

Team Size: 1

Duration: 9 Months

Description: With the increasing features in Teradata. The Memory consumption has also increased. In Earlier versions like before v2r6, Reusage of memory has not been implemented. In TD12.0.2 and higher the resuage of memory was introduced as sql’s working prior to TD12 were failing in higher releases. This project was developed to handle the memory consumption in qrw and optimizer modules. This was one of the complex projects and received appreciation for the work done.

Received Compliments from the development for the work done in this project.

5. Project Name: Enhancing the Deadlock detection logic in Join Planning.

Team Size: 1

Duration: 6 Months

Description: Teradata is a cost based approach. When an SQL is run which is having no of tables optimizer does a Join Planning by taking all the possibilities to join the tables and picks the join which is very cheap for a better join plan. During this process in optimizer it also checks that the join planning doesn’t involve in a deadlock. To ensure this an algorithm is there which checks if deadlock is possible or not. But is missed a case when there are nested sub queries with more that 5 nesting levels and correlation is there between outer level and the nested level. This project was developed to handle the problematic issue.

6. Project Name: Join Plan Related Problems.

Team Size: 1

Duration: 6 Months

Description: This project was developed to handle wide range of problems which occurred in the optimizer phase. Problems like Join Term not being consumed after the complete processing is over. Mapping of the Fields to the correct relation after the Join has been done between two tables. Handling of the Exists Term in complex join processing. This is one of the complex project since it has to embed the code in one of the complex modules in optimizer.

Qualification: M.Tech(CSE) from Osmania Univ with 73%

(GATE Score: 97.13%).

Technical skills:

Languages known : C, C++, SQL,

Interesting Subjects : Operating Systems, Computer Organization.

Operating Systems : Dos, Windows, Unix.

Databases : Teradata.

Personal Profile:

Name : M.MANIK PRABHU

Father Name : M.RUKMAIAH

Date of Birth : 24-08-1980

Address : M.Manik Prabhu, S/o M.Rukmaiah, 1-59/61/B Flat-20A, Blk-B, Sai Krupa Apartments,

Madinaguda Near Madinaguda Masjid, Miyapur

Hyderabad-500049.

Email id : ***********@*****.***, ***********@*****.***

Hobbies : Playing Chess, Solving Puzzles.

Strength’s : Logical reasoning, Programming skills, Hard working.

Languages known: Telugu, Hindi and English.

Place : Hyderabad

Date : (M.Manik Prabhu)

Contact this candidate