Database Analyst (MS Access and SQL) is a 6+ month contract role with RedSalsa Technologies in Columbus, OH. The position is onsite with a hybrid mix and interviews are virtual. This role directly involves a legacy Microsoft Access front end with a SQL Server back end that is currently in production and being modernized toward a web-based Azure solution.

What the role entails: You will be working hands-on with an existing Microsoft Access application that serves as the user interface for a SQL Server database used by the Ohio Division of Oil & Gas Resources Management. The work includes resolving bi-directional data sync issues, writing T-SQL queries, stored procedures, and triggers, cleaning up orphaned data, supporting ETL processes, and helping define a roadmap to sunset the Access front end as the system transitions to a web-based platform. You will also act as a proxy product owner, participate in Agile ceremonies, document requirements, and help test and validate system enhancements.

About RedSalsa Technologies: RedSalsa is a consulting and staffing firm that supports government and enterprise clients on complex data, application modernization, and infrastructure projects. This role supports a state government agency and involves a long-running, mission-critical system that is actively being transitioned rather than abruptly replaced.

Rick's take: This is a great real-world Access job, even though the long-term goal is to retire the Access front end. That is exactly how many Access careers actually work. You are supporting, stabilizing, and extending an existing Access application while helping plan the migration path forward. This is not beginner-level work. You need solid Access, VBA awareness, and strong SQL Server skills. Students who have completed my Access Developer series and understand how Access fits into a larger SQL Server ecosystem would be very well positioned here. This job is a perfect example of why Access is still in demand, especially in government environments where legacy systems live for a long time. Remember how long some of those COBOL programmers had jobs supporting software written in the 60s.