Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-10-25 : 08:50:52
|
| Jason writes "Have complicated scenario to explain so i will do my bestwith it. Here is the situation: Trying to replicate an as/400 to a SQL Server 2000 box using data mirror 4.6... Here is my dilema. If my operations group restores the as/400 to a certain marker, how do you identify the recordson the SQL side that need to be updated/deleted, etc, so acomplete refresh of data is not needed? Currently, we havea 3 day refresh period due to this issue, and i cant see howthat is acceptable. The main reason for this is because thelarge table is a loan history table, but it can be updated,so it isnt much of a history table so to speak. I would like to create a stage table that houses 7 days worthof data, and then delete the pervious 7th day at close of business to keep the record count down. Data mirror would handle that subscription. from there, SQL server would pushthe new records, updates, deletes, etc, to the final tablewhich would include all dates, including the data that is inthe stage table. the problem comes in when the as/400 is restored,and i assume that i can delete the dates that i have in SQLthat the restore DIDNT include, what happens if a new transactioncoming from the as/400 is an update rather than an insert? therecord doesnt exist for that date anymore because i deleted it toavoid dups. I know data mirror 5.2 will insert the record if itdoesnt exist even on an update, but we are using 4.6... Has anyone dealt with this before? It has been an issue for yearsand there have been many consulting companies they have paid a lotof money to figure this out, and they have yet to be able to. Aminterested to hear if anyone has dealt with this situation before. Thanks in advance!Jason" |
|
|
|
|
|
|
|
AS400 ---> SQL Server 2000