How can I connect on two databases (same structure) but located on two differents servers?

I want to copy data from one to the other.

thanks

Benoit

1) Use Adapter 2) Use Adapter 3) Use Adapter

This is important

All you need to do is create two instances of DataAccessAdapter, one pointing to each database. You can then load enties using one adapter and save them using the other one.

The trick to make sure that the entities save properly in the new database is to set .IsNew = true and .IsDirty = true on the entity and .IsChanged on each field in the entity

This will ensure that the second adapter thinks that each field needs to be saved and the entity needs to be inserted rather than updated.

Matt

Any way to do it with self-servicing? ;-)

Benoit

Erm. no - sorry - with the way SS is designed it makes this sort of data manipulation impossible.

To be honest, in 5 years of using LLBLGen professionally I've never found any situation where SelfServicing offered any advantage over adapter - the overhead in using adapter is minimal (one extra project and no lazy loading) but the flexibility it gives you is a massive advantage.

Matt

an alternative could be the RDBMS native data import/export features. Most databases have these kind of tools which are in general very fast (as you have the same structure, so bulk copy etc. is ideal)

What about using a transaction?

        DocumentCollection localDocs = (DocumentCollection)DocumentsDataSource.EntityCollection;


        Transaction tx = new Transaction(IsolationLevel.Serializable, "LiveData",  LiveSqlConnectionString);
        try
        {
            foreach (DocumentEntity localDoc in localDocs)
            {
                DocumentEntity liveDoc = new DocumentEntity();
                tx.Add(liveDoc);
                liveDoc.FetchUsingPK(localDoc.Id);
                liveDoc.Title= localDoc.Title;
                ...
                liveDoc.Save();
            }

            tx.Commit();
        }
        catch (Exception)
        {
           ...
        }
        finally
        {
            tx.Dispose();
        }

It does seem to work quite well, did I overlook something?

Benoit

It works. The thing is how this is setup in your application context. If that application have multiple users, you might experience problems for sure. If this is just a tool that you run once, you could do what you are doing (fetch with some connection, save with another). You also could use DBUtils.ActualConnectionString for this, but transaction is a good idea to make the save action atomic.