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

VB 6.0 applications needs to replicate data Expand / Collapse
Author
Message
Posted Wednesday, September 25, 2013 4:02 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Tuesday, September 23, 2014 4:37 AM
Points: 746, Visits: 1,058
Hi,

I have an application in VB 6.0. That application needs to replicate some data to another database (different database).

The goal is to make something (SSIS, WebService or Replication) that can send information to the other database.

The production environment particular situation:

1) The internet is very low (speed) and sometimes it goes down.
2) The other place (where the other database is) sometimes has internet other times it does not have.


Based on this problematic situation, what I need is to create something (SSIS, WebService or Replication) that can always see if the internet is available and when it is, start replicating the data.

What is the best thing to do? SSIS, WebService or Replication?

Thanks

Post #1498225
Posted Wednesday, September 25, 2013 11:14 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 10:20 PM
Points: 3,008, Visits: 2,608
If the 3 options you list, only one of them will automatically resume processing following a network outage. This is replication. In your environment, you would need to make sure that you set the appropriate properties on the distribution agent so that it is more resilient to network outages. The sort of options you need to consider include batch and transaction size and timeout durations.

SSIS packages are usually scheduled to run at particular time(s) of the day. So it the network is down, it won't automatically retry. It will fail if the network is down. The next time it is scheduled to run, is the next time it will attempt to replicate data.

WebServices, of themselves, do not do anything unless an application makes of request. Webservices are normally written so that you make a request (e.g. give me some data please). The webservices responds with the data that satisfies you request and then it stops processing. If you wrote the webservice to replicate data when you made the request, it would behave a bit like the SSIS package...it would attempt to connect, potentially fail, return some success or failure status and then go back to sleep.



Post #1498670
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse