Talend has a free community edition and a DB2 journal...

Eugene Elutin (3/12/2012)

---

Jeff Moden (3/12/2012)

---

For the most part, I agree but there are some grand exceptions. There are many places where T-SQL code will beat SQLCLR simply because the...

HowardW (3/12/2012)

---

You could use one of the 3rd party SCD merge components[/url], but I'd tend to just insert everything into a staging table first, then join that to the main...

No, I'm sorry.

Are you facing some issues?

Great, glad you solved your issue.

Linked Servers are not intended for that kind of stuff. OLEDB has a great overhead and is not the ideal tool for massive data movement.

I would suggest trying with SSIS.

Sure it works, but it won't use indexes.

I would recommend using dynamic SQL in this case.

You can look it up in Erland's article.

Sounds tasty!

A bit hypercaloric, but tasty! 😛

😀 You made my day!

I can go home happy now!

I would not rely on DATENAME.

Try prefixing that code with SET LANGUAGE Italian:

L'impostazione della lingua è stata sostituita con Italiano.

-----------------------

2011-12-31 00:00:00.000

(1 row(s) affected)

I got the newsletter as usual. No issues here.

With 5 update queries working on the same remote data set, I would download the remote table locally to a temp table.

Have you tried that?

The most likely cause is a predicate that doesn't get pushed to the linked server and gets resolved locally, after copying the entire remote table in tempdb.

I would try to...

In as few words as possible: don't trust it when it's high, start worrying when it's low.

You're right Jeff (as usual)!

Thanks for pointing it out.