Accessing (writing into) Terdata by ado.net and SSIS

Hello everybody,

my name is Christof and I#m currently trying to write into our Terdata Warehouse by SSIS. In the Management Studio we can perfectly access Terdata - reading from it - but we actually see no way writing back Data into that system. Is there any hidden feature, any configuration menu that we had′nt seen so far?.

In the software documentation we found a tip "ADO.NET" as Data Destination is′nt imlemented for now - please wait until ....

I′m asking me if someone has had the same problem before and could help me out with a little tip.

thx in advance!

Christof

Moved to the SSIS forum. It doesn't sound like you're having a problem with ADO.NET itself, but rather how to get SSIS to do what you want, so I think this is the best place to start.

Thanks,
Sarah

Accessing (writing into) Terdata by ado.net and SSIS

Hello everybody,

my name is Christof and I#m currently trying to write into our Terdata Warehouse by SSIS. In the Management Studio we can perfectly access Terdata - reading from it - but we actually see no way writing back Data into that system. Is there any hidden feature, any configuration menu that we had′nt seen so far?.

In the software documentation we found a tip "ADO.NET" as Data Destination is′nt imlemented for now - please wait until ....

I′m asking me if someone has had the same problem before and could help me out with a little tip.

thx in advance!

Christof

Good luck with non-SQL Server destinations.

Read through here for tips: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=106559&SiteID=1

Access to the ADO.net Managed Provider SqlClientFactory was denied

In a previous post in Installation and Setup I was having problems just getting an ASP.NET 2.0 app to run on my web server. Now I'm having some different weird security issues.

I'm getting this message when just trying to open a database and put its contents into a gridview.

Access to the ADO.net Managed Provider 'SqlClientFactory' was denied in the data source with ID 'sqlEmployees' because of security settings.

I think this may have to do with our web server and our SQL server being separate machines. That always gives us issues. But I have impersonation=true in my web.config along with windows authentication and I have SQL Server configured with Windows and SQL authentication so things should be right, I'm thinking.

Any ideas??

I guess I stumped everyone. Thanks anyways.|||

Did you find the solution? If so please post it, so that it will help others :)

|||Had the same problem. There was a web.config in the root directory, deleted it and solved the problem