Wednesday, March 28, 2012

RMO Programming in VB.net

Hi,

Currently I am using the BCP functionality to import/export tables between different SQL Server 2005 databases. The process is working ok, but it creates alot of manual work, when 70 or more tables need to be transferred, every week. I am new to RMO development and am interested if the following may be possible.

- I would like to build an interface in VB.net allowing users to select a source database, and select the tables that need to be transferred from the Source DB, to the Destination DB.

-Put in place RMO funtionality to replicate the source database tables into flat files.

-Within the Vb.net app transfer the created flat files into the destination database.

I would greatly appreciate any advice on this, or if there may be a better approach at replacing the BCP functionality.

Thanks,

Since the number of tables needed will vary from user to user, then it might make sense to stick with what you have or use DTS or SSIS in some way. YOu can get creative by setting up Snapshot Replication and use your VB app to read the BCP files from the snapshot folder, but that could get tricky.

|||

Thanks Greg.

If the tables were to remain consistant would an RMO approach be feasible?

|||

Yes, if the tables were to remain constant then you could create a snapshot publication (assuming you don't need up-to-the-minute changes) and use RMO to create or sync your subscriptions. More detail/information regarding your app and business requirements would be helpful, but yes, this should work for you. You can read more about RMO in books online, just search for RMO. You can also read up on the different types of replication and what snapshot, transactional and merge replication have to offer.

|||

hi,

i saw this post & i also want to implemnt an vb.net application to provide replication.

so incase u have made the application plz guide me to make the same for my organisation.

i m also new to sql RMO

i actually made it with sql SMO

No comments:

Post a Comment