Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS Logging - start and end dates Expand / Collapse
Author
Message
Posted Tuesday, July 16, 2013 5:04 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:31 PM
Points: 5,158, Visits: 12,001
We use a fairly detailed level of logging within our packages.

It's configured for each package by selecting the SSIS / Logging / Details / Advanced tab.

There is no obvious way to select StartTime and EndTime for every row which is logged - they appear to be mandatory.

OK, we can live with that. But we've noticed that, for every row, the values for StartTime and EndTime are identical. Our log table is currently 70 million rows in size, so that's not a small sample.

Do others see the same thing? Are these values ever different?




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

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.


  Post Attachments 
Logging.png (4 views, 23.40 KB)
Post #1474063
Posted Tuesday, July 16, 2013 5:39 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 1:42 PM
Points: 13,239, Visits: 11,018
Never really payed attention to it, but you're right. I just ran a package with every possible log event enabled, but the columns are still the same.
So you can basically ignore the endtime column.




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

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1474072
Posted Tuesday, July 16, 2013 6:08 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:31 PM
Points: 5,158, Visits: 12,001
Koen Verbeeck (7/16/2013)
Never really payed attention to it, but you're right. I just ran a package with every possible log event enabled, but the columns are still the same.
So you can basically ignore the endtime column.


Thanks for confirming that we are not alone - that's an awful lot of wasted disk space around the world.



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

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.
Post #1474082
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse