Just thinking out load (because its good to get feedback)
Dont suppose anyone has a clever way of scheduling sql jobs? Looking at you @jamiet
— Matt Smith (@matt40k) February 9, 2016
Just to expand on my tweet. I’ve lot of SSIS packages for load and building my BI warehouse (SSAS cubes), now currently I have a SQL job that has multiple steps
- Load data from Source system into Staging
- Build ODS intermediate tables
- Build Warehouse tables
And this works for DataMart where they are a denormalized copy of a single source system, but when the source system, or the intermediate tables, are used multiple times, you don’t want to run them multiple times. Equally I don’t want to figure this out each time we add a new package.
I basically want a controller task that manages it.
We have a automation build\deploy process, so you commit the (SSDT\SSIS\SSAS) packages and it deploys it and creates a SQL job for each SSIS package. We could add step to trigger the controller to update the schedules based on the change.
Now we would need to define the dependencies, basically we need build a hierarchy. Technically I could read the SSIS packages then parse the select statements then create some logic to work it out automatically, but for now, it’ll be a static table(s).
So. Do I create a SQL stored procedure to create a SQL job(s) with multiple steps or a SSIS package using something like BIML?