Microsoft SQL Server 2012 Integration Services (SSIS) provides significant improvements in both the developer and administration experience. This article provides tips that can help to make the upgrade to Microsoft SQL Server 2012 Integration Services successful. The tips address editing package configurations and specifically connection strings, converting configurations to parameters, converting packages to the project deployment model, updating Execute Package tasks to use project references and parameterizing the PackageName property.
- TIP #1: Edit Package Configuration and Data Source after upgrading
- TIP #2: Convert to project deployment model using Project Conversion Wizard
- TIP #3: Update Execute Package Task to use project reference and use parameter to pass data from parent package to child package
- TIP #4: Parameterize PackageName property of Execute Package Task to dynamically configure which child package to run at execution time
- TIP #5: Convert package configuration to parameter when possible
Download Whitepaper Download Whitepaper 5 Tips for a Smooth SSIS Upgrade to SQL Server 2012
Above text is taken from original msdn documentation.
Reference: Pinal Dave (https://blog.sqlauthority.com)
I created a customer table and booking table, I had inserted the data for customer record, but how to insert records into Booking table for customer that customer who books?
Dear Pinal, I installed SQL 2012. I created SSIS package which has Script Task. When I right click on it and say edit..Edit script… I get following error:
Can you please help to resolve this issue?
TITLE: Microsoft Visual Studio
Cannot show Visual Studio 2010 Tools for Applications editor.
Could not load file or assembly ‘Microsoft.VisualStudio.Tools.Applications.Core, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified. (mscorlib)
Hi, I am also getting the same error as above. Could you please let me know the resolution for this issue?
I am also getting the same error and couldn’t find out much information from Blogs / MSDN either, can someone please suggest?
I too am facing the same error. Anyone got some suggestion?
I had the same error. I fixed it by uninstalling the VSTA runtime (add remove programs) and then running repair on SSDT (SQL installation media)
i am facing the same situation as rohini, has anyone managed to solve the problem?