Quantcast
Channel: SQLServerCentral » Data Warehousing » Analysis Services » Latest topics
Viewing all articles
Browse latest Browse all 1341

XP_SQLAGENT_ENUM_JOBS vs. SP_HELP_JOB

$
0
0
Let me start at the beginning. Here is what we are doing:1. Control-M calls... 2. A Batch File that calls...3. A Stored Procedure that runs...4. A SQL Agent Job that processes...5. An SSAS cube.The status of the SQL Agent Job must ultimately be returned to Control-M.Yes, I know that we can have Control-M process the SSAS cube directly, thereby bypassing all of those steps. However, that is not what the company wants, not my decision :-).Anyway, I am using XP_SQLAGENT_ENUM_JOBS in my stored procedure to periodically retrieve the status of the job instead of SP_HELP_JOB. I know that XP_SQLAGENT_ENUM_JOBS is undocumented. However, I decided against using MSDB.dbo.sp_help_job because:1. It generally requires OPENROWSET to put the resultset into a table, which requires additional overhead of an OLEDB connection. 2. It outputs more columns than xp_sqlagent_enum_jobs, which might also impact performance. Is my reasoning sound? What are the counter arguments.

Viewing all articles
Browse latest Browse all 1341

Trending Articles