diffrent duration every time excute the same package
Hi all , i was asking if this normal to have a differnt duration value for my SSIS every time i execute ? i have one SSIS 2008 and running on SQL Server 2008 x64 thanks in advance
July 11th, 2011 1:21pm

this maybe because server workload, maybe server resources taken or released at the time of running the package, and this will cause execution time of package.http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2011 1:25pm

What is your package doing? Is the data it's processing exactly the same every time it runs?Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings MC ID: Microsoft Transcript Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
July 11th, 2011 1:42pm

Hi all , i was asking if this normal to have a differnt duration value for my SSIS every time i execute ? i have one SSIS 2008 and running on SQL Server 2008 x64 Are you running the package manually in BIDS or on a server? If you are running in BIDS: you can't really do performance testing inside BIDS itself. You better execute the package with the DTEXEC utility. And what are different duration values exactly? A few seconds. Don't sweat it. 30 minutes? Then there is something going on.MCTS, MCITP - Please mark posts as answered where appropriate.
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2011 2:00pm

I am ruunign the packge using DTEXEC utility, the SSIS funcation is mainly import data from multiple datasources (SQL 2008 on diff servers using linked server)and export them to flat files (excel,txt,...) and in osme other steps executing SQL scripts calling stored proceduers the first duration was 1.30 houre and the seconde execution is 45 min my SSIS function is fixed which mean it does the same every time execute it .... no workload on the server and the SSIS package is still in the test envireoment and didn't deploye on the online server
July 11th, 2011 3:26pm

could you tell us more about your package schema? control flow and data flow both? what tasks? precedence constraint? sources/transformations/destinations in data flow?http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2011 3:29pm

Maybe the results from the stored procedures were cached? The network was slower the first time? But an half hour is indeed a big difference. Now, to conclude anything that is statistically relevent, you need to execute the package a few times, so that you can get an average runtime. By the way, linked servers, can't you connect directly to those servers?MCTS, MCITP - Please mark posts as answered where appropriate.
July 11th, 2011 3:30pm

Hi all , i was asking if this normal to have a differnt duration value for my SSIS every time i execute ? i have one SSIS 2008 and running on SQL Server 2008 x64 thanks in advance Yes, it is normal.http://sqlblog.com/blogs/jamie_thomson/ | @jamiet | About me
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2011 3:44pm

Hi all , i was asking if this normal to have a differnt duration value for my SSIS every time i execute ? i have one SSIS 2008 and running on SQL Server 2008 x64 thanks in advance Yes, it is normal. I don't consider a 30 minute difference between executions of the same package on the same server with no other workloads normal.MCTS, MCITP - Please mark posts as answered where appropriate.
July 11th, 2011 3:50pm

Hi Jamie, i'd be greatly appriciate if there is a technical reason in order to tell my customer... as they have some business need to know an occurate number of the duration and they asked why it took diffrent duration .. so technical explination should satisify them
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2011 4:08pm

I would like to give you my thoughts: while I am almost sure your duration varies due to "multiple datasources" you will need some evidence to defend your findings, such a tool could be DTLoggedExec http://dtloggedexec.davidemauri.it/default.aspx?AspxAutoDetectCookieSupport=1 You can use it to generate stats from each run even though you do not have the logging enabled. These stats can be turned into reports that you can use to find out where the extended duration is and present your finding to the customer.Arthur My Blog
July 11th, 2011 4:32pm

thanks for sharing your though , but they are satisifed with the max duration which is 1.30 hour and they don't need to know which part is take long time , they just need to know the duration actually they just asked one of these dummy question and i have to explain why it take sometimes 1.30 hour and other rime 45 min ... :)
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2011 4:40pm

thanks for sharing your though , but they are satisifed with the max duration which is 1.30 hour and they don't need to know which part is take long time , they just need to know the duration actually they just asked one of these dummy question and i have to explain why it take sometimes 1.30 hour and other rime 45 min ... :) Well, without any form of logging or looking at the package itself, we can't tell that for you. We can just guess...MCTS, MCITP - Please mark posts as answered where appropriate.
July 11th, 2011 4:43pm

I am agree with Koen, you can add logging to your scenario, and we can talk better about result thenhttp://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2011 4:51pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics