Sql DBA

Redolent Infotech Pvt. Ltd.; Bentonville (AR); On-site; USD 90,000 - 120,000; Full time

Job summary

Redolent Infotech Pvt. Ltd. is seeking a SQL DBA in Bentonville, AR for a 6+ month engagement.

The role requires 3–5 years of SQL Server experience, T‑SQL proficiency, and strong skills in HA, backups, and migrations. The candidate will drive cloud-first migration plans, evaluate Azure IaaS/PaaS options, and coordinate with app owners to ensure a smooth transition. The project involves deploying SQL Servers on both cloud and on-premise environments, setting up failover and AlwaysOn DAGs, and

Qualifications

• 3–5 years experience with Microsoft SQL Server RDBMS (2008R2–2017 migrations).
• Strong knowledge of SQL and T-SQL.
• Experience with SQL Server installations and upgrades; Azure portal familiarity.
• Understanding of HA features (AlwaysOn, DAG) and backups/recovery.
• Ability to coordinate with application owners and migration teams.

Responsibilities

• Lead migrations to Azure Cloud or on-premise as approved by the app team.
• Deploy SQL Server on IaaS/VMS and manage database migrations.
• Configure and test AlwaysOn or DAG for multi-node clusters and DR.
• Manage database backups, maintenance tasks, and failover procedures.
• Communicate migration plans, pros/cons, and timelines to stakeholders.
• Decommission old SQL Server instances after migration.

Skills

SQL Server

T-SQL

PowerShell

Azure

Windows OS

High Availability

Backups & Recovery

Communication

Job description

We have following urgent role with our DIRECT client

Title: Sql DBA

Location: Bentonville, AR

Duration: 6+ Months

Rate: Market Microsoft SQL Server DBA

Required:

• 3 to 5 years experience with Microsoft SQL Server RDBMS platform – SQL Versions: 2008R2, 2012, 2014, 2016, 2017 migrations.
• Knowledge of structured query language (SQL); i.e. Transact-SQL.
• Knowledge of SQL Server Installation and upgrades (in-place vs side-by-side upgrades). General knowledge of the Azure portal. Ability to navigate the portal effectively. Knowledge on PowerShell and how to use SQL Server and Azure modules. General understanding of the Windows operating system.
• In-depth Knowledge about SQL High Availability features like mirroring, AlwaysOn, Distributed Availability Groups (DAG). Understanding of database backups, recovery, and handling failover of a database. General understanding of routine database maintenance.
• General understanding of distributed computing i.e. Client- server model.
• Ability to effectively communicate with application owner for obtaining information driving migration success.
• Identifying SQL Server 2008/R2 from SQL DBA Inventory and obtaining the owner information
• Communicate w/ App team owners including necessary detail on migrations outlining steps and pros/cons for using a new version of SQL Server.
• The first / preferred option is to migrate to Azure Cloud. We'll request app team for Sherpa consultation using this link to determine a roadmap for Azure IaaS/PaaS.
• If app team can't proceed with Cloud deployments, they will need the Sherpa team to approve that decision.
• If Cloud is supported/approved, DBA team will assist on deploying SQL Servers (IaaS) via Managed Services.
• If direction is approved for on-premise, app team will coordinate with Windows team on getting VMs and DBA team will install/configure SQL Server on on-premise VMs.
• After SQL Database engine is installed, the databases will need to be migrated to the (new) destination servers.
• For Point-In-Time data, mirroring will need to be setup and 'failed over' during the switch.
• For 2 or more node clusters, database(s) will be added to the Availability Group (i.e. AlwaysOn Availability Group). For Azure Production servers, we will configure Distributed Availability Groups (DAG) for Disaster Recovery.
• SQL Logins, Jobs will be migrated as well.
• Verify and migrate other services were used i.e. Integration Services, Full Text Indexes (if necessary)
• Also, verify and other dependencies that need to be moved / re-created on the destination server.
• Ensure connections have been pointed to the new server and rename databases on the old server.
• Decommission the old servers.