Well it's a new-ish SQL2008 SP1 x86 box so there shouldn't be any 2005 there. I'll have more of a poke about, thanks.

Hi Ritesh,

Yes, we think it is now resolved. It seems that we were pulling too much data from a Sybase database over a linked server, using the OPENQUERY command....

What kind of connection managers are you using? The ADO.Net ones I find to be pretty much unusably slow. The old OLEDB ones work well with large datasets.

Well, I solved it. The service pack unchecked the 'allow inprocess' checkbox for the linked server provider!

No queries work. Even expanding the linked server node no longer works (timeout).

We have tried registering new linked servers with the same details, and while they register, they also...

My destination is SQL Server 2008. I used ADO.Net as it was the most modern technology so I assumed it would at least work well, if not offer some...

Yeah mine was too. The file hadn't copied correctly.

Was it definitely a problem with the backup? I am having the same issue.

Yeah, it's the EncryptSensitiveWithPassword option that fails validation.

It's on the same server. The connection is made in the sybase data source adminstrator and is an oledb connection. There seems to be no way to specify...

I would try passing your arguments as strings instead of datetimes. I have found both sybase and SSIS to be rather inconsistent when using datetime values (loss of precision...

That worked great, thanks!

I am having the same problem on 2008 server, connecting to ASE 15. It's only for one table though, but it's a table I really need. I can...

And the Import/Export wizard does not seem to work with the Sybase drivers.

When I choose the Sybase OLEDB Provider, I then click Properties.. and populate the connection details....

This is too big and repetitive to be built visually. Can someone point me in the direction of how I can approach this programatically?