Hi,

I can't possibly find any information of actually how to use a data source object or a data source view object in a package.

After I've added a SQL Server data source object and a data source view object to my project I can't use any of them in almost any of the source or destination data flow component.

I've created an entry for the Data Source in the Connection Manager pane, but the only connection where I can see the Data Source object listed is in the DataReader source component. It lists the Data Source object amongst all available connections to use. Is this all? What am I doing wrong?

Moreover, I can't find any option to add a Data Source VIEW object to anything. How am I supposed to use this kind of object in SSIS?

Thanks for enlightening me!

Axel Dahmen

Hi Axel,

Data Source's should be available in any source task that supports the
type of connection (OLEDB source for OLEDB connection). However, I
would advise against using Data Sources. At first glance, you would
think they are a nice way to manage connections across multiple
packages, but in reality changing the data source still forces you to
open every task that uses that connection and refresh the metadata(!)
IIRC there are also issues with configuration as the DS doesn't really
belong to any particular package, but rather to the solution.

DSV's are not used in SSIS at all.

Good luck!
J

Hi Axel,

Data Source's should be available in any source task that supports the
type of connection (OLEDB source for OLEDB connection). However, I
would advise against using Data Sources. At first glance, you would
think they are a nice way to manage connections across multiple
packages, but in reality changing the data source still forces you to
open every task that uses that connection and refresh the metadata(!)
IIRC there are also issues with configuration as the DS doesn't really
belong to any particular package, but rather to the solution.

DSV's are not used in SSIS at all.

Good luck!
J

Hi Axel,

Data Source's should be available in any source task that supports the
type of connection (OLEDB source for OLEDB connection). However, I
would advise against using Data Sources. At first glance, you would
think they are a nice way to manage connections across multiple
packages, but in reality changing the data source still forces you to
open every task that uses that connection and refresh the metadata(!)
IIRC there are also issues with configuration as the DS doesn't really
belong to any particular package, but rather to the solution.

DSV's are not used in SSIS at all.

Good luck!
J

Hi Axel,

Data Source's should be available in any source task that supports the
type of connection (OLEDB source for OLEDB connection). However, I
would advise against using Data Sources. At first glance, you would
think they are a nice way to manage connections across multiple
packages, but in reality changing the data source still forces you to
open every task that uses that connection and refresh the metadata(!)
IIRC there are also issues with configuration as the DS doesn't really
belong to any particular package, but rather to the solution.

DSV's are not used in SSIS at all.

Good luck!
J

Hi Axel,

Data Source's should be available in any source task that supports the
type of connection (OLEDB source for OLEDB connection). However, I
would advise against using Data Sources. At first glance, you would
think they are a nice way to manage connections across multiple
packages, but in reality changing the data source still forces you to
open every task that uses that connection and refresh the metadata(!)
IIRC there are also issues with configuration as the DS doesn't really
belong to any particular package, but rather to the solution.

DSV's are not used in SSIS at all.

Good luck!
J

Hi Axel,

Data Source's should be available in any source task that supports the
type of connection (OLEDB source for OLEDB connection). However, I
would advise against using Data Sources. At first glance, you would
think they are a nice way to manage connections across multiple
packages, but in reality changing the data source still forces you to
open every task that uses that connection and refresh the metadata(!)
IIRC there are also issues with configuration as the DS doesn't really
belong to any particular package, but rather to the solution.

DSV's are not used in SSIS at all.

Good luck!
J

Hi Axel,

Data Source's should be available in any source task that supports the
type of connection (OLEDB source for OLEDB connection). However, I
would advise against using Data Sources. At first glance, you would
think they are a nice way to manage connections across multiple
packages, but in reality changing the data source still forces you to
open every task that uses that connection and refresh the metadata(!)
IIRC there are also issues with configuration as the DS doesn't really
belong to any particular package, but rather to the solution.

DSV's are not used in SSIS at all.

Good luck!
J

Hi Axel,

Data Source's should be available in any source task that supports the
type of connection (OLEDB source for OLEDB connection). However, I
would advise against using Data Sources. At first glance, you would
think they are a nice way to manage connections across multiple
packages, but in reality changing the data source still forces you to
open every task that uses that connection and refresh the metadata(!)
IIRC there are also issues with configuration as the DS doesn't really
belong to any particular package, but rather to the solution.

DSV's are not used in SSIS at all.

Good luck!
J

Hi J,

thanks again for your helpful response.

I had the impression before that Data Sources and Data Source Views are more or less abandoned concepts. I still have the impression that SSIS is more or less beta.

So you suggest I should refrain from trying to use Data Source objects and Data Source Views? I don't see an advantage in Data Source objects if one still has to wade through each connection object referencing it.

Best regards,
Axel Dahmen



------------------------
<jhofmeyr (AT) googlemail (DOT) com> schrieb im Newsbeitrag news:357f3f7c-38b9-4366-a886-ec7297e85ea3 (AT) e39g2000hsf (DOT) googlegroups.com...