<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Data Warehousing
»
Integration Services
»
T-SQL Merge over databases in different...
T-SQL Merge over databases in different servers
Rate Topic
Display Mode
Topic Options
Author
Message
Paul Hernández
Paul Hernández
Posted Thursday, March 14, 2013 3:01 AM
SSC Journeyman
Group: General Forum Members
Last Login: Today @ 5:34 AM
Points: 75,
Visits: 264
Hi Folks,
I would like to know if it´s possible to use the T-SQL MERGE if the source DB is a DB2/AS4000 in a remote server, and the target is a SQL DB in the local server.
Any comment would be appreciated.
Kind Regards.
Paul Hernández
http://hernandezpaul.wordpress.com/
https://twitter.com/paul_eng
Post #1430819
Phil Parkin
Phil Parkin
Posted Thursday, March 14, 2013 3:08 AM
SSCarpal Tunnel
Group: General Forum Members
Last Login: Today @ 2:19 PM
Points: 4,324,
Visits: 9,665
Paul Hernández (3/14/2013)
Hi Folks,
I would like to know if it´s possible to use the T-SQL MERGE if the source DB is a DB2/AS4000 in a remote server, and the target is a SQL DB in the local server.
Any comment would be appreciated.
Kind Regards.
I doubt it, given that DB2 SQL is a different language from T-SQL.
Why have you posted this in the Integration Services forum, by the way?
____________________________________________________________________________________________
Help us to help you. For better, quicker and more focused answers to your questions, consider following the advice in this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
If you are asking for help and your post does not contain a question, you should expect responses which do not contain any answers. Put a question mark in there somewhere - it's not rocket science.
Post #1430824
Paul Hernández
Paul Hernández
Posted Thursday, March 14, 2013 3:42 AM
SSC Journeyman
Group: General Forum Members
Last Login: Today @ 5:34 AM
Points: 75,
Visits: 264
Hi Phil,
Thanks for your quick answer.
Then I will create a temporal table to store the records to be update, and then perform a batch or bulk update, I think it is the best option since use a "OLE DB Command" component is too slow.
I posted it here, because this issue is a part of an ETL proccess and I´m comparing loading strategies, but it could also be posted in the SQL Server 2008 forum.
Kind Regards,
Paul Hernández
http://hernandezpaul.wordpress.com/
https://twitter.com/paul_eng
Post #1430837
Phil Parkin
Phil Parkin
Posted Thursday, March 14, 2013 3:46 AM
SSCarpal Tunnel
Group: General Forum Members
Last Login: Today @ 2:19 PM
Points: 4,324,
Visits: 9,665
Paul Hernández (3/14/2013)
Hi Phil,
Thanks for your quick answer.
Then I will create a temporal table to store the records to be update, and then perform a batch or bulk update, I think it is the best option since use a "OLE DB Command" component is too slow.
I posted it here, because this issue is a part of an ETL proccess and I´m comparing loading strategies, but it could also be posted in the SQL Server 2008 forum.
Kind Regards,
Sounds like a good option. I think you meant 'temporary' rather than temporal. If not, I'd like to know how you would use a temporal table here.
____________________________________________________________________________________________
Help us to help you. For better, quicker and more focused answers to your questions, consider following the advice in this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
If you are asking for help and your post does not contain a question, you should expect responses which do not contain any answers. Put a question mark in there somewhere - it's not rocket science.
Post #1430840
Paul Hernández
Paul Hernández
Posted Thursday, March 14, 2013 3:50 AM
SSC Journeyman
Group: General Forum Members
Last Login: Today @ 5:34 AM
Points: 75,
Visits: 264
Hi Phil,
It was a language mistake due to my level of English, which sometimes is not good enough
You are right; the correct term is
“temporary”
Thanks for your remark.
Paul Hernández
http://hernandezpaul.wordpress.com/
https://twitter.com/paul_eng
Post #1430841
Phil Parkin
Phil Parkin
Posted Thursday, March 14, 2013 3:53 AM
SSCarpal Tunnel
Group: General Forum Members
Last Login: Today @ 2:19 PM
Points: 4,324,
Visits: 9,665
Paul Hernández (3/14/2013)
Hi Phil,
It was a language mistake due to my level of English, which sometimes is not good enough
You are right; the correct term is
“temporary”
Thanks for your remark.
No problem. That's a shame - I was quite looking forward to an innovative temporal solution
____________________________________________________________________________________________
Help us to help you. For better, quicker and more focused answers to your questions, consider following the advice in this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
If you are asking for help and your post does not contain a question, you should expect responses which do not contain any answers. Put a question mark in there somewhere - it's not rocket science.
Post #1430843
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
