Inventory Data Consolidation to SQL
Budget: $30 – $250 USD
I have several disparate sources holding our inventory information and I want it all pulled together into one clean, well-structured Microsoft SQL Server database file. The job is straightforward in principle: extract every piece of inventory data you can reach, reconcile duplicate SKUs or mismatched item descriptions, then load the final result into a single .sql or .bak file that I can restore through SQL Server Management Studio.
Please preserve every existing field that carries operational value—quantities on hand, reorder thresholds, location codes, cost figures, and any audit timestamps—and normalise the schema where it clearly improves reporting speed or data integrity. If a field appears under different names in different systems, map it consistently; if you uncover gaps, flag them so I can decide whether to fill or discard.
I will consider the task complete when I can:
• restore or run the script on my Microsoft SQL Server instance without errors,
• query a consolidated Items table and see one row per unique SKU,
• join stock levels to their warehouse locations with no orphan records, and
• export a sample CSV of current inventory that matches today’s live figures.
T-SQL proficiency is essential; SSIS, Azure Data Studio, or any other ETL tooling you prefer is fine as long as the final deliverable is the ready-to-go SQL Server file described above.
Please preserve every existing field that carries operational value—quantities on hand, reorder thresholds, location codes, cost figures, and any audit timestamps—and normalise the schema where it clearly improves reporting speed or data integrity. If a field appears under different names in different systems, map it consistently; if you uncover gaps, flag them so I can decide whether to fill or discard.
I will consider the task complete when I can:
• restore or run the script on my Microsoft SQL Server instance without errors,
• query a consolidated Items table and see one row per unique SKU,
• join stock levels to their warehouse locations with no orphan records, and
• export a sample CSV of current inventory that matches today’s live figures.
T-SQL proficiency is essential; SSIS, Azure Data Studio, or any other ETL tooling you prefer is fine as long as the final deliverable is the ready-to-go SQL Server file described above.
Related categories:
.NET
SQL
Microsoft Access
Database Administration
Microsoft SQL Server
Data Integration
ETL
Database Design