Thursday, March 10, 2011

BIDS slower than DTEXEC !

I Recently came accross two important that I would like to share articles regarding that topic.

http://blogs.msdn.com/b/mattm/archive/2011/01/15/why-does-my-package-run-slower-in-bids-than-dtexec.aspx?wa=wsignin1.0

http://sqlblog.com/blogs/jamie_thomson/archive/2011/01/12/always-use-dtexec-exe-to-test-performance-of-your-dataflows-no-exceptions.aspx


Helpful Dtexec.exe cheats:

To execute an SSIS package saved to SQL Server using Windows Authentication:
dtexec /sq pkgOne /ser productionServer

To execute an SSIS package saved to the File System folder in the SSIS Package Store:
dtexec /dts "\File System\MyPackage"

To validate a package that uses Windows Authentication and is saved in SQL Server without executing the package:
dtexec /sq pkgOne /ser productionServer /va

To execute an SSIS package that is saved in the file system:
dtexec /f "c:\pkgOne.dtsx"

To execute an SSIS package that is saved in the file system, and specify logging options:
dtexec /f "c:\pkgOne.dtsx" /l "DTS.LogProviderTextFile;c:\log.txt"

To execute a package that uses Windows Authentication and is saved to the default local instance of SQL Server, and verify the version before it is executed:
dtexec /sq pkgOne /verifyv {c200e360-38c5-11c5-11ce-ae62-08002b2b79ef}

To execute an SSIS package that is saved in the file system and configured externally:
dtexec /f "c:\pkgOne.dtsx" /conf "c:\pkgOneConfig.cfg"


More here http://msdn.microsoft.com/en-us/library/ms162810.aspx