Hi,
I was wondering if anybody could give me some information on Oracle's replication limitations when it comes to attempting to replicate between two DBS's that are not always connected to each other (ie. network connection down or phone line down).
Does SQL Server have a built in 'queuing' process that will hold onto data that needs to be replicated and then when connection is obtained it will replicate at that time? Or is there a third party tool that is needed to handle this?
I have worked with Sybase before to handle this type of replication and they have separate products (can't remember what they are called at this time) that are needed that handles that data that needs to be replicated.
If you could point me to some link (or book) that I could read up on this (I have the documentation but it really doesn't get into this to well) it would be greatly appreciated.
Thanx,
JB
I was wondering if anybody could give me some information on Oracle's replication limitations when it comes to attempting to replicate between two DBS's that are not always connected to each other (ie. network connection down or phone line down).
Does SQL Server have a built in 'queuing' process that will hold onto data that needs to be replicated and then when connection is obtained it will replicate at that time? Or is there a third party tool that is needed to handle this?
I have worked with Sybase before to handle this type of replication and they have separate products (can't remember what they are called at this time) that are needed that handles that data that needs to be replicated.
If you could point me to some link (or book) that I could read up on this (I have the documentation but it really doesn't get into this to well) it would be greatly appreciated.
Thanx,
JB