May 29, 2015 at 11:12 am
Our group had recently moved a lot of older SQL Server 2005 databases and BI tools to use with SQL Server 2012 and DTS. I have one such project to update for which I have modified the initial SQL code to add two new fields, a couple of lookup codes, and changing the name of two other fields. However these minimal changes have created a multitude of problems with the remaining down-stream data flow components and paths that I just cannot resolve. I, nor anyone else left here, do not have a lot of experience with SSIS and editing Data Flows. I have included an attachment PHT SSIS Project DataFlow.doc file with a screen shot of the project Data Flow and a copy of the current SQL in a .doc attachment along with a description of the initial problems.
My specific problems after saving the top level SQL to pull data from a Legacy database to update the current web-project database in SQL Server 2012, is that the original field names of changed fields are not automatically changed in data flow paths and although I can remove them, it does not allow me to re-add them with the new names nor does it allow me to add the new fields to source and destination column maps via the component/path editors or advanced editors. The top level component takes the changed SQL just fine but its data flow path has invalid entries and missing entries that I cannot correct and which snow-ball going down the data flow paths. Please help me understand and repair this mess.
"Any fool can write code that a computer can understand. Good programmers write code that humans can understand." -- Martin Fowler
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply