RE: Replication between as/400 and Sql Server 2000

It all depends on what information you want to extract.

If you need only a few data items, I'd choose for the trigger process.
If you need large variety of data, you are probably better off with a generic 
journalling application.

Dirk.


-----Original Message-----
From:   Lopez, Eduardo   (Tijuana) [SMTP:lopeze@xxxxxxxxxxxxxxxxx]
Sent:   Friday, July 11, 2003 8:37 AM
To:     'SSA's BPCS ERP System'
Subject:        RE: Replication between as/400 and Sql Server 2000

Dirk,

I thought about that... but journaling is almost the same as triggers... the
thing is that if I implement triggers it'll take me more time to implement
them... or it won't? what do you think?

Regards,
Eduardo

>-----Original Message-----
>From: Dirk De Moitie [mailto:midi@xxxxxxxxxx] 
>Sent: Thursday, July 10, 2003 1:07 PM
>To: 'SSA's BPCS ERP System'
>Subject: RE: Replication between as/400 and Sql Server 2000
>
>
>Why don't you just put a DB trigger each time you 
>update/delete such a file ? The trigger can pass on your data 
>in the format you need.
>
>Ultamatly, you might even invoke a remote procedure 
>and write straight into your SQL server database.
>
>
>Dirk.
>
>
>
>-----Original Message-----
>From:  Nathan Bennett [SMTP:nabennis@xxxxxxxxx]
>Sent:  Thursday, July 10, 2003 9:31 PM
>To:    SSA's BPCS ERP System
>Subject:       RE: Replication between as/400 and Sql Server 2000
>
>What makes you think the DB journalling will impact the 
>iSeries so much?
>
>I'll assume your going to 'pick' the files you want to 
>replicate so it's not the entire database.  With the correct 
>use of ASP's and other techniques you can reduce the impact on iSeries.
>
>Regards
>Nathan
>
>-----Original Message-----
>From: bpcs-l-bounces@xxxxxxxxxxxx 
>[mailto:bpcs-l-bounces@xxxxxxxxxxxx]On
>Behalf Of Lopez, Eduardo (Tijuana)
>Sent: Thursday, July 10, 2003 3:54 AM
>To: 'bpcs-l@xxxxxxxxxxxx'
>Subject: Replication between as/400 and Sql Server 2000
>
>
>Hi to all,
>
>I have a big "dilemma"... hope somebody can help... this is my 
>situation
>
>We want to built a custom data warehouse with SQL Server for 
>the QMS, API and CAP modules... why use SQL Server?...
>
>   * We already have the license for SQL Server 2000 
>Enterprise this means that we can use Analysis Services for 
>free... the product/solutions from IBM and also from Cognos 
>are very expensive!!
>   * We'll be very integrated with Microsoft Office... using 
>for example Pivot Tables, the Office Web Components, etc... 
>and for free because we already have the licenses for Microsoft Office
>   * The time to implement it is very short... three months!!
>   * We already have all the tools from the Windows side
>   * I'm very skilled in SQL Server
>
>
>Please follow..
>I'm evaluating a replication tool... the tool name is 
>DB2Motion from Hit Software... this tool operates in two modes 
>refresh and mirroring... the first one uses the DB2 Journal 
>feature which is very cool because we can have in some parts 
>of the data warehouse "real-time" data!! and the other mode is 
>using primary keys on the tables to get the last records (not 
>real-time data)... and now my "dilemma"
>
>   * I can't use the DB2 Journal feature because it'll impact 
>to much the
>as/400... so this means that I can't use "real-   time" 
>data... that's fine
>for now...
>   * I can't use primary keys because the BPCS tables doesn't 
>have primary keys!!... Ohh my god why?
>
>the only "good" option that I can think is using the ODBC 
>driver from Hit Software or the one from IBM's Client/Access 
>with the Data Transformation Services (DTS) feature from SQL Server
>
>Can somebody guide me on any more options... there has to be 
>another way...
>
>Thank you,
>
>Eduardo Lopez
>Software Developer
>Tyco Adhesives
>
>US Phone (San Diego, CA)
>+1  (619) 424-4244
>Mexican Phone (Tijuana, MX)
>+52 (664) 647-4359
>
>"Man finds God behind every door that science manages to open" 
>"El hombre encuentra a Dios detras de cada puerta que la 
>ciencia logra abrir" Albert Einstein
>
>_______________________________________________
>This is the SSA's BPCS ERP System (BPCS-L) mailing list
>To post a message email: BPCS-L@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
>or email: BPCS-L-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/bpcs-l.
>
>_______________________________________________
>This is the SSA's BPCS ERP System (BPCS-L) mailing list
>To post a message email: BPCS-L@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
>or email: BPCS-L-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/bpcs-l.
>
>
>
>
>
>_______________________________________________
>This is the SSA's BPCS ERP System (BPCS-L) mailing list
>To post a message email: BPCS-L@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
>or email: BPCS-L-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/bpcs-l.
>
_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.