Blog

Must Have:

1. 4-6 years experience
2. Reporting & performance tuning
3. PL/SQL, MySQL
4. AWS – how to scale, set up clusters

Responsibilities:
 
• Need someone to help re-architect and redesign the way this database is organized to eventually help build a new reporting platform.
• Come in and help optimize database and queries to help with reporting functionality
• This is critical to fix and implement
• We are seeking an AWS Database Developer with extensive hands-on experience with large-scale database migration projects to AWS, particularly Oracle to AWS Aurora and Redshift
• Experience in Oracle database 11g and above Extensive knowledge in Oracle SQL
• Proficiency in AWS data services such as Aurora, Redshift, S3, Athena, Glue, and R3 Spectrum
• Deep understanding of cloud-native data architecture principles and best practices
• Expertise in database performance optimization, troubleshooting, and tuning in cloud environments
• Excellent knowledge of SQL, ETL processes, and data modeling
• tables, indexes, partitions, DB links, and experience in Oracle Advanced Pl/SQL
• Experience in tuning SQL queries & PL/SQL code for optimum performance
 
Review & propose:

1. Schemas and database server, in the queries being executed.
2. Propose solution for SQL long queries.
3. SQL queries to improve performance.
4. Monthly Reports solutions for all equipment at customer level.
5. Design database structure for planned projects like file Management and Smart Tag.
6. Optimize Queries – Ensure that queries are properly optimized.
7. Tables and create indexing. Ensure that tables are indexed on columns frequently used in WHERE clauses, JOIN conditions, and ORDER BY clauses.
8. Adjust database configuration parameters (such as memory allocation, cache sizes, and connection limits) to match the hardware resources and workload of our system.
9. Add partitioning and sharding to distribute load if required.
10. Large tables, consider partitioning them based on certain criteria (such as range or hash partitioning).
11. Evaluate database schema and consider normalizing or de-normalizing it based on the Current KC requirements.
 
Long Term :

Reporting Strategy

1. Purpose reporting tool for automated report and dashboard.
2. Establish a reporting cadence that provides timely insights without overwhelming stakeholders.
3. Balance frequency with the availability of relevant data and the need for real-time decision-making.