Connectivity validation against the Skyworks Operational Data Store (ODS) environment. Database and SSIS access are confirmed, and the SQL Server Agent job inventory on the production instance has been reviewed in full.
The access points below were reviewed. Connections to the SQL Server database and the SSIS package network folder were established with no issues, and the complete SQL Server Agent job inventory has since been reviewed on the production instance.
Metadata captured via a direct catalog query against the production instance. All accessible databases are online, on SQL Server 2017 (compat level 140), SIMPLE recovery. Three databases hold ~86% of the ~6.9 TB footprint. SkySTRMPS is excluded (access not provided).
| Database | Size (MB) | Tables | Views | Stored Procs | Schemas | Established |
|---|---|---|---|---|---|---|
| Skyworks_ODS_Archive | 900,464 | 485 | 37 | 61 | 25 | 2019 |
| SkyBuy | 56,325 | 24 | 16 | 4 | 4 | 2019 |
| SAP_Snapshot_AdvPlan | 15,800 | 47 | 6 | 9 | 10 | 2019 |
| SkyEO | 3,180 | 10 | 2 | 0 | 1 | 2019 |
| SCM | 3,106 | 34 | 293 | 55 | 3 | 2020 |
| SkyCRM | 2,800 | 66 | 0 | 0 | 1 | 2019 |
| SkyQuote | 1,240 | 30 | 15 | 0 | 1 | 2019 |
| SkyFoundry | 375 | 58 | 24 | 0 | 1 | 2019 |
| SkyExpense | 260 | 23 | 2 | 0 | 1 | 2019 |
| SkySamples | 125 | 15 | 1 | 7 | 1 | 2019 |
| SkyProductDocuments | 110 | 1 | 0 | 0 | 1 | 2019 |
| SkyCentral | 85 | 10 | 5 | 3 | 2 | 2019 |
| SkyAllocate | 80 | 18 | 0 | 31 | 1 | 2019 |
| SkyEOL | 60 | 16 | 0 | 0 | 1 | 2019 |
Skyworks_ODS is the heart of the operational data store. Schema names map to functional domains. Top twelve by table count:
The SSISDeployment network folder was reviewed directly and correlated against the complete SQL Server Agent job inventory. None of the 589 SSIS job steps reference packages through the MSDB catalog; all resolve to a file path.
A small number of packages reside in Clone subfolders (Skyworks_ODS\rr and Skyworks_ODS\scm); these are excluded from the 563 count. All three are actively referenced by enabled Agent jobs, so they are in current use, not orphaned copies.
Every one of the 589 SSIS job steps points to a file in the network folder; none use the MSDB catalog (/DTS or /SQL), so package lineage maps cleanly onto the deployment folder.
A complete extract of the production SQL Server Agent covers every subsystem type. 304 jobs carry at least one SSIS execution step; the remainder are predominantly T-SQL (3,701 steps for internal monitoring, alerting, and maintenance), with smaller numbers of PowerShell, Analysis Services, replication, and log-reader jobs.
Of the 312 packages referenced by Agent jobs, 26 were not found in the network folder: 12 in Costing, 3 in SkySubConCommit, 2 in RR, and the rest across FI, MD, and SCM. One job (Monarch) points to a separate E:\SSISHR\Deployed\ share, outside the scope of this pass. At 19.6% inactive, production is far leaner than the 69% inactive seen in QA.
LIB_ECC_RTP (~2.6 TB), Skyworks_ODS (~2.0 TB), and Skyworks_WH (~1.2 TB) dominate the ~6.9 TB footprint across the 17 in-scope databases. Profiling effort concentrates here.
30 job steps read the local path E:\Project\FlatFileDataSources\ directly; a further 36 exchange flat files through JDA shares and SFTP. These upstream and downstream flows are inventoried during lineage mapping.
79 packages are invoked by more than one Agent job. The most reused, Exec_RR_Script.dtsx, runs from 38 different jobs with different runtime parameters (plant code, environment), so one package node can represent many logical data flows.
197 of 1,006 jobs (19.6%) are inactive, well below the 69% inactive seen in QA. Production keeps a more actively maintained footprint, though a modest legacy population remains for review during lineage mapping.
Connectivity to the provided production systems is validated. Two workstreams now run in parallel.
Prepared by Findability Sciences as part of the Skyworks Solutions ODS Assessment engagement. Read access is confirmed across the accessible in-scope databases, and the SSIS package landscape has been catalogued. The SQL Server Agent job inventory of 1,006 jobs has been reviewed in full. The engagement now proceeds to metadata inventory and package parsing.