February 6, 2017 at 10:54 am
I am having an issue with my SSIS 2016 Package in VSTS 2105. I have four packages in a solution and none of the packages are overly complex. When I open any of the packages or try to code them, each mouse click is taking 10 to 20 minutes to respond. I have already tried setting Delay Validation to True as well as setting the Work Offline option. I have even copied the packages to a new solution, but I get the same behavior. This seemed to start happening around the time that I added an expression to a variable that referenced a Project.params environment variable which is a simple integer value of 18. @[User::vETLMinimumStartDate] = (DT_WSTR, 50) (DT_DBDATE) DATEADD( "Month", - @[$Project::env_ETLMonthsOfHistory] , DATEADD( "Day", -1,GETDATE()) )@[User::vETLMinimumStartDateKey] = (DT_I4) ( SUBSTRING( @[User::vETLMinimumStartDate] , 1, 4 ) + SUBSTRING( @[User::vETLMinimumStartDate] , 6, 2 ) + SUBSTRING( @[User::vETLMinimumStartDate] , 9, 2 ))
There is no error or issue with variables or the expression as they both do exactly what I need them to do. I have even gone as far as running Repair on Visual Studio from the Control Panel
Does anyone have any idea what is going on here and what I can do get things working again?
February 6, 2017 at 11:06 am
michael.french 172 - Monday, February 6, 2017 10:54 AMI am having an issue with my SSIS 2016 Package in VSTS 2105. I have four packages in a solution and none of the packages are overly complex. When I open any of the packages or try to code them, each mouse click is taking 10 to 20 minutes to respond. I have already tried setting Delay Validation to True as well as setting the Work Offline option. I have even copied the packages to a new solution, but I get the same behavior. This seemed to start happening around the time that I added an expression to a variable that referenced a Project.params environment variable which is a simple integer value of 18.@[User::vETLMinimumStartDate] = (DT_WSTR, 50) (DT_DBDATE) DATEADD( "Month", - @[$Project::env_ETLMonthsOfHistory] , DATEADD( "Day", -1,GETDATE()) )@[User::vETLMinimumStartDateKey] = (DT_I4) ( SUBSTRING( @[User::vETLMinimumStartDate] , 1, 4 ) + SUBSTRING( @[User::vETLMinimumStartDate] , 6, 2 ) + SUBSTRING( @[User::vETLMinimumStartDate] , 9, 2 ))
There is no error or issue with variables or the expression as they both do exactly what I need them to do. I have even gone as far as running Repair on Visual Studio from the Control PanelDoes anyone have any idea what is going on here and what I can do get things working again?
This is strange and I have no idea what the problem is. But if it was me, I'd create another solution and try adding copies of the packages to it, one at a time, and see what happens. Maybe there's one specific package which is causing the issue. Or maybe it's a strange project setting.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
February 17, 2017 at 8:41 am
I found the answer. What I had done was assigned the value to the variable in the Expression of the variable.
@[User::vETLMinimumStartDate] = (DT_WSTR, 50) (DT_DBDATE) DATEADD( "Month", - @[$Project::env_ETLMonthsOfHistory] , DATEADD( "Day", -1,GETDATE()) )
While the correct evaluation was returned, apparently it did so in a big recursive loop that somehow ended.
When I removed the assignment, the project returned to normal operating performance from VSTS.(DT_WSTR, 50) (DT_DBDATE) DATEADD( "Month", - @[$Project::env_ETLMonthsOfHistory] , DATEADD( "Day", -1,GETDATE()) )
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply