May 8, 2017 at 8:56 am
Has anyone had any issues (slow) running a 2012 package directly on a 2016 server?
May 8, 2017 at 9:39 am
d_george - Monday, May 8, 2017 8:56 AMHas anyone had any issues (slow) running a 2012 package directly on a 2016 server?
Is the slowness occurring in ExecuteSQL tasks, by any chance?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 8, 2017 at 9:47 am
Hello and thank you.
I haven't broken it down into parts, I first I looked to see if there was a known issue.
Can I take that to mean you have seen a decrease in speed and that you have traced it to those particular tasks?
May 8, 2017 at 9:52 am
d_george - Monday, May 8, 2017 9:47 AMHello and thank you.
I haven't broken it down into parts, I first I looked to see if there was a known issue.
Can I take that to mean you have seen a decrease in speed and that you have traced it to those particular tasks?
Not the tasks, per se, but the fact that the Cardinality Estimator has changed fairly drastically between 2012 and 2016. So the same query may run slower in 2016 than on 2012.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 8, 2017 at 9:57 am
Thank you.
I'll see if I can isolate the drain.
May 8, 2017 at 10:39 am
Out of curiosity, when you say "running a 2012 package directly on a 2016 server" you mean that you built up the SSIS package in the 2012 BIDS and then deployed it to a 2016 SSIS server, correct?
I have had odd issues when I have used 2016 SSMS to deploy a package to a 2012 SSIS server. Even browsing the 2012 SSIS catalog from a 2016 SSMS I have found to be abnormally slow.
When doing stuff with SSIS, I strongly encourage you to use the same SSMS version when deploying, configuring and executing to reduce the chance of errors.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply