Calculated column not showing
Hi All! I'm new to SSIS.. What I'm trying to do is to use named calculations in a DSV. I created the DSV with a single table from a relational database. The table has 2 columns and I added 2 named calculations. Everything is fine...I can preview the data, and it's ok When I try to use the DSV in an OLE DB Source, I do select the DSV in the connection manager list, then select the table...but the calculated columns do not show up when I click the Preview button What am I missing?? thanks!
October 24th, 2010 10:57pm

Data Source Views are not required for creating SSIS Packages. I would go straight to the Server/database in question and use that for the Connection Manager. If you need to create a calculated column, do it in a Derived Column Transform in the Data Flow.Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.
Free Windows Admin Tool Kit Click here and download it now
October 25th, 2010 1:37am

Data Sources and Data Sources views should never be used in SSIS. Those are artifacts that are required and very helpful in other type of BIDS projects (eg. SSAS), but in SSIS create an unnecessary abstraction layer that create a lot of issues. I would try to create additional columns directly in the source query or, as suggested by Todd, in a derived column. I wish BIDS will prevent you from using DS an DSVs in a SSIS project - or at the very least give you a warning.Help Others! Don't forget to mark your thread as answered
October 25th, 2010 3:59am

Data Sources and Data Sources views should never be used in SSIS. I disagree. Creating a Shared Data Source for as SSIS Project allows one to easily create Connection Managers for the individual packages within the project. Every package that references that Shared Data Source will get updated if you need to change the definition of it. Comes in handy when you have 50 packages all referencing the same Data Source that gets moved. Doesn't replace Configurations, obviously, but I find them usefull none the less.Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.
Free Windows Admin Tool Kit Click here and download it now
October 25th, 2010 4:13am

I respect your opinion about using data sources in SSIS. In my experience they are not useful at all as the connection information is just copied into each package. You could argue that it saves you few clicks (if any) when adding a connection to the package for the first time. As per the 'convenience' of changing connections across multiple packages - that is just half way true as that only works at design time. Additionally, you are likely to receive annoying warning messages at design time stating the DS and connection managers are out of sync each time you or other developer happens to change the .ds definition. That is a night mare in multi developer environments. If you think they are helpful, just keep using them.Help Others! Don't forget to mark your thread as answered
October 25th, 2010 5:12am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics