Home/ Questions/Q 4066880
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T16:10:53+00:00

I’m doing a data migration at the moment of a subset of data from

  • 0

I’m doing a data migration at the moment of a subset of data from one database into another.

I’m writing a .net application that is going to communicate with our in house ORM which will drag data from the source database to the target database.

I was wondering, is it feasible, or is it even a good idea to put the entire process into a transaction scope and then if there are no problems to commit it.

I’d say I’d be moving possibly about 1Gig of data across.

Performance is not a problem but is there a limit on how much modified or new data that can be inside a transaction scope?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There’s no limit other than the physical size of the log file (note the size required will be much more then the size of the migrated data. Also think about if there is an error and you rollback the transaction that may take a very, very long time.

    If the original database is relatively small (< 10 gigs) then I would just make a backup and run the migration non-logged without a transaction.

    If there are any issues just restore from back-up.

    (I am assuming that you can take the database offline for this – doing migrations when live is a whole other ball of wax…)

    If you need to do it while live then doing it in small batches within a transaction is the only way to go.

    • 0