This project is read-only.

2012 support?

Topics: Developer Forum
May 12, 2012 at 7:22 PM


do you plan support for 2012, and if so can you roughly specify time when it could be published? If you need a help with that, I'd be happy to participate...



May 22, 2012 at 4:33 PM

Hi Radim

Currently, there are no plans to port DTLoggedExec to SQL Server 2012 since the changes introduced with this release of Integration Services offers the same features the DTLoggedExec offers, and more.


May 25, 2012 at 4:42 PM

Hello, manowar I'm trying to run a DTSX package on a SSIS 2012 64 bit machine running it with dtexec.exe /FILE "D:\MAIN.dtsx" /CONFIGFILE "D:\Import.dtsConfig"  /MAXCONCURRENT " -1 " /CHECKPOINTING OFF  /REPORTING EWCDI > Log_DTEXEC.txt, this package fails and in Log_DTEXEC.txt there is the following error Description: The SSIS logging provider has failed to open the log. Error code: 0x80070003.

I'd like to better investigate this error with a tool like DTLoggedExec but it seems to be not supported, you suggest that SQLSERVER 2012 contains new feature can explain how to use this feature to identify the problem?



Dec 11, 2012 at 10:00 AM

Hi Manowar

Yes if its posible to setup SSIS 2012 so it can make some good logging like DTLoggedExec I would like to know or have a link to some documentation.... Because I'm really missing my DTLoggedExec (that I have used on SQL 2008 R2) on my new DW on SQL 2012 ;-)



Dec 19, 2012 at 12:03 PM


Found it :-) SSIS Catalog

BR Kurt

Dec 19, 2012 at 1:28 PM


Jun 13, 2016 at 1:10 PM
Hi Manowar

I do agree with you that SSIS 2012 and newer have out of the box logging which would do in most cases.
However that logging is only available if the package is executed from the catalog, not if it is executed from the filesystem.

e.g. if we run the package from a .ispac or from a package deployment model then SSIS catalog logging is not done.

This means that processes like those used on my shop where we create the packages on the fly becomes quite cumbersome as it also requires each package to be saved to the catalog - meaning either recreate all packages before executing them and saving them as part of one project, or save each package as individual projects on the catalog.

would be great if you could provide a version for 2012+