February 19, 2018 at 6:39 am
Is there a bug with SSDT 2015 also regarding the Script Task component? If I set it to use VB as main language, after deploying it basically loses its previous settings and I need to recreate it again and again. This doesn't allow me to schedule the project through a SQL Job...
Thanks
February 19, 2018 at 6:43 am
caf 13920 - Monday, February 19, 2018 6:39 AMIs there a bug with SSDT 2015 also regarding the Script Task component? If I set it to use VB as main language, after deploying it basically loses its previous settings and I need to recreate it again and again. This doesn't allow me to schedule the project through a SQL Job...Thanks
Same as this? You are not alone.
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
February 19, 2018 at 6:45 am
caf 13920 - Monday, February 19, 2018 6:39 AMIs there a bug with SSDT 2015 also regarding the Script Task component? If I set it to use VB as main language, after deploying it basically loses its previous settings and I need to recreate it again and again. This doesn't allow me to schedule the project through a SQL Job...Thanks
Yep, happened for me as well. Will need to report a bug to MS
February 19, 2018 at 6:46 am
No results from Microsoft so far? This is so frustrating... I think I might go back to use SSDT 2012
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply