Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

T-SQL Merge over databases in different servers Expand / Collapse
Author
Message
Posted Thursday, March 14, 2013 3:01 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, August 18, 2014 5:26 AM
Points: 119, Visits: 483
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
Posted Thursday, March 14, 2013 3:08 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 2:06 PM
Points: 5,047, Visits: 11,797
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.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.
Post #1430824
Posted Thursday, March 14, 2013 3:42 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, August 18, 2014 5:26 AM
Points: 119, Visits: 483
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
Posted Thursday, March 14, 2013 3:46 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 2:06 PM
Points: 5,047, Visits: 11,797
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.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.
Post #1430840
Posted Thursday, March 14, 2013 3:50 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, August 18, 2014 5:26 AM
Points: 119, Visits: 483
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
Posted Thursday, March 14, 2013 3:53 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 2:06 PM
Points: 5,047, Visits: 11,797
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.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.
Post #1430843
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse