Job Role and Responsible

The SQL Database Administrator (DBA)

 I am working  closely with our organization’s business managers, business users, application developers, and network team to model, design, and monitor database systems (currently MS SQL Server).

Intricate customer facing  within the customers environment  discussion technical and business teams to devise and recommend solutions based on the understood requirements , project management and risk mitigation

Deliver customer Cloud Strategies, aligned with customers business objectives and with a focus on Cloud Migrations

As a leader of the team/project, ensure success in designing, building and migrating applications, databases, and services on the AWS platform Help to design and implement AWS RDS, Aurora and/or Redshift architectures and configurations for customer Think strategically about business, product, and technical challenges in an enterprise environment.

Design and deploy enterprise-wide scalable operations on Cloud solution. 

Design and strategize on security of the cloud environment

Provide leadership in infrastructure migration methodologies and techniques including mass application movements into the cloud including implementation of  AWS within in large regulated enterprise environments.

Analyze on premise transactional database environments such as Oracle, SQL Server, MySQL and/or Postgres, evaluate and plan migrations to AWS RDS, Aurora

Participate in architectural discussions and design exercises to create large scale solutions built on AWS and also be part of the development lifecycle.

The SQL DBA role and responsible for establishing database business rules, maintaining documentation of data and reporting protocols,and assisting in the development and implementation of best practices for the management of databases including the assurance of database policies

and procedures, data integrity, data extraction, report customization, and analysis.

database up and running smoothly 24/7. The goal is to provide a seamless flow of information throughout the company, considering both backend data structure and frontend accessibility for end-users.

 

•  Review project requests describing database user needs to estimate time and cost required to  accomplish project 

•  Review procedures in database management system manuals for making changes to database 

•  Work as part of a project team to coordinate database development and determine project scope and limitations 

•  Identify and evaluate industry trends in database systems to serve as a source of information and advice for upper management

-------------------------------------------------------------------------------------------------------

Virtusa's offerings include end-to-end migration including discovery, planning, analysis, migration, and optimization with program management oversight. Virtusa's factory is based on a migration pipeline supported by best-of-breed tools and specialized, core/flex teams.

Phases of migration

• Phase 1: Prepare

You identify the interdependencies between your applications and databases. You also analyze the database workloads to determine the migration categories: from simple rehost (homogeneous) migration to re-architect (heterogeneous) migration.

These tasks are discussed in the following sections:

•         Identifying dependencies àBy asking questions such as

§  Is this database directly accessed by any other application?

§  Is the database using database links to fetch data from other databases?

•         Qualifying workloads à Understand the current database workload

§  workload qualification tool called AWS Workload Qualification Framework (AWS WQF)

§  It helps identify the complexity of your Oracle and Microsoft SQL Server database migration by analyzing database schemas and code objects, application code, dependencies, performance characteristics.

• Phase 2: Plan 

The 6 most common application migration strategies we see are:

§  Re-host (Referred to as a “lift and shift.”)

§  Re-platform (Referred to as “lift, tinker, and shift.”)

§  Re-factor / Re-architect

§  Re-purchase

§  Retire

§  Retain (Referred to as re-visit.)

•         Migration Readiness and Planningà(MRP) is a method that consists of tools, processes, and best practices to prepare an enterprise for cloud migration. MRP describes a specific program that AWS Professional Services offers

•          

• Phase 3: Migrate (p. 8)

• Phase 4: Operate and optimize (p. 13)

 ----------------------------------------------------------

Engage customers in pre-sales, technical discussions

Determine customer cloud-readiness

Migration strategies affect architectural decisions

Identify tools to use for assessing and analyzing  migration readiness


identify a customer strengths and weaknesses for cloud readiness

TOC-total cost of ownership

   TSO Logic --collector method /

   Migration Portfolio Assessment (MPA) -->right sizing ,on-premises and aws comparisons, total cost ownership/migration project cost estimates

Tool 

Cloud adoption readiness tool (CART)

    -->self-service evaluation

    -->Plans for cloud adoption

Migration Readiness Assessment (MAR)