Hi there-
I've had various PDI scripts running since early 2015 -- they are unrelated except they are all run by a master job in PDI (version 5.4.0.1), on the same remote computer, and to the same SQL Server data warehouse.
For the last two nights, they've all been running about 20-30x slower.
What are some potential tests I can do to determine what is causing this across the board?
Moreover, at least for now (around noon as opposed to midnight when these scripts typically run, along with other processes) -- it seems instead of taking about 30x longer (whoof) --- they are only now taking 2x as long, making it harder to find the source.
I can test the SQL database but I have a hunch that isn't it.
What else can be going on here? The remote computer is shared - but I find it highly unlikely a change was made after Friday night (it ran just fine then).
Maybe it was connectivity issues (database is on a network with PDI ETL machine) -- but yeah, I'm not sure. Maybe I need more granularity in performance of each step.
I've had various PDI scripts running since early 2015 -- they are unrelated except they are all run by a master job in PDI (version 5.4.0.1), on the same remote computer, and to the same SQL Server data warehouse.
For the last two nights, they've all been running about 20-30x slower.
What are some potential tests I can do to determine what is causing this across the board?
Moreover, at least for now (around noon as opposed to midnight when these scripts typically run, along with other processes) -- it seems instead of taking about 30x longer (whoof) --- they are only now taking 2x as long, making it harder to find the source.
I can test the SQL database but I have a hunch that isn't it.
What else can be going on here? The remote computer is shared - but I find it highly unlikely a change was made after Friday night (it ran just fine then).
Maybe it was connectivity issues (database is on a network with PDI ETL machine) -- but yeah, I'm not sure. Maybe I need more granularity in performance of each step.