SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS package last date/ time run


SSIS package last date/ time run

Author
Message
krishnaprasad14
krishnaprasad14
SSC-Addicted
SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)

Group: General Forum Members
Points: 411 Visits: 1022
Hi,

How to find date/time last SSIS packgae ran.

Please let me know if you need any other details ..

Thanks In Advance,

-Krishna
Tim Mitchell
Tim Mitchell
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: General Forum Members
Points: 1827 Visits: 2988
You won't find that information in the package itself. If you have logging set up on the package, the logging information will give you that information. If you're using the SQL Server Agent to execute the package, you'll find the execution information in the Agent log (although it's still possible that the package could still have been executed outside of SQL Server Agent).

If you're using SSIS 2012 in catalog deployment mode, you can check the SSIS catalog tables for execution information.



Tim Mitchell, Microsoft Data Platform MVP
Data Warehouse and ETL Consultant
TimMitchell.net | @Tim_Mitchell | Tyleris.com
ETL Best Practices


Koen Verbeeck
Koen Verbeeck
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27725 Visits: 13268
Tim Mitchell (9/5/2013)
You won't find that information in the package itself. If you have logging set up on the package, the logging information will give you that information. If you're using the SQL Server Agent to execute the package, you'll find the execution information in the Agent log (although it's still possible that the package could still have been executed outside of SQL Server Agent).

If you're using SSIS 2012 in catalog deployment mode, you can check the SSIS catalog tables for execution information.


And if you really want to be thorough, you can combine all three! :-D


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
krishnaprasad14
krishnaprasad14
SSC-Addicted
SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)

Group: General Forum Members
Points: 411 Visits: 1022
Thank you for your reply...

-krishna
Phil Parkin
Phil Parkin
SSCoach
SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)

Group: General Forum Members
Points: 18861 Visits: 20460
Koen Verbeeck (9/5/2013)
Tim Mitchell (9/5/2013)
You won't find that information in the package itself. If you have logging set up on the package, the logging information will give you that information. If you're using the SQL Server Agent to execute the package, you'll find the execution information in the Agent log (although it's still possible that the package could still have been executed outside of SQL Server Agent).

If you're using SSIS 2012 in catalog deployment mode, you can check the SSIS catalog tables for execution information.


And if you really want to be thorough, you can combine all three! :-D


It sounds over the top, but I do quite often check all three!


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
herladygeekedness
herladygeekedness
Mr or Mrs. 500
Mr or Mrs. 500 (516 reputation)Mr or Mrs. 500 (516 reputation)Mr or Mrs. 500 (516 reputation)Mr or Mrs. 500 (516 reputation)Mr or Mrs. 500 (516 reputation)Mr or Mrs. 500 (516 reputation)Mr or Mrs. 500 (516 reputation)Mr or Mrs. 500 (516 reputation)

Group: General Forum Members
Points: 516 Visits: 813
We like to have that info right in the warehouse table and I have a morning job that checks for stale data and alerts us. Pkgs can run successfully yet not refresh the data so we prefer the data to tell us last successful run.

I have a variable in each package that I set to GetDate() , then assign that variable to a field to output with the data.

This has eliminated all guesswork on the part of the users - we show last refresh date on charts in the dashboard so they know As Of immediately. They can always ask for an update if it's not new enough for their purposes but this heads off the "I was looking for a special case I was investigating, but don't see it here ..." tickets.

Wasn't quite sure of your purpose so put it out there in case you aren't asking "for you".
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search