Moving a large MS Sql Database

Im looking for a way to move a large MS Sql Database without taking a full backup and copying it over to new server.

Is there a way to copy database today.
Then the next day only copy over what has changed since last copy?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Alexey KomarovChief Project EngineerCommented:
From the beginning you need to restore full backup in norecovery mode.
Then you need to restore all transaction log backup's.
k3vsmithAuthor Commented:
Ok, so your saying copy full backup over to server. Then restore full backup in norecovery mode. I will have to look up how to do that.
Then your saying I should be able to copy over transaction log backups from point of time I took full backup to time I want to cutover to new server?
Look at log shipping or db mirroring

There is no good way to do what you want without backup/restore.
Make sure you copy the SQL logins from your current server to the new one.
The backup retains the security credentials references, however Usera with password some password on server A is not the same account on server b, unless both have the same Sid.

Ms has SQL login transfer that can easily be found via a search on the web.
If you need it and can not find it ..

When restoring either tsql or using the SQL server management graphical restore db,, including the norecovery in the tsql or selecting the middle option on the options as Alexey pointed meaning the DB at the conclusion on the new server will remain in recovery mode and will not be brought online. This is needed for the option of restoring transaction logs either manually (backup transaction log, copy, restore with the same norecovery option) or setting up log shipping that will automate this process, or configure the DB in db mirroring setup which will in real-tine update the new server when changes are made on DB on server A.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Alexander ArdatovSoftware ManagerCommented:
You can try to use copy-only full and tlog backups. It will not break current backup chain.
k3vsmithAuthor Commented:
Thanks. We are going to try mirroring.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.