|
|
Posted by Mark D Powell on 08/17/06 23:15
Erland Sommarskog wrote:
> Stu (stuart.ainsworth@gmail.com) writes:
> > the safest method is to do a backup and restore; however, you can
> > detach, move, and reattach (usually) with no problems. Of coruse,
> > before doing any operation such as this, you should take a backup first
> > (which is why the first method is recommended).
>
> The advantage with detach/attach is that you don't have to wait for
> the new data file to be initiated. For a 3GB database that's maybe 5-10
> minutes on SQL 2000. SQL 2005 has some quick initiation under some circum-
> stances.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
OK, the plan is
1- that the customer is going to try to lock the end-users out of the
application
2- I will backup the database
3- I will detatch it
4- I will copy the files to the new location
5- I will attach the db
6- I will test accessing some data
7- the customer will open the application
In the event of serious problems I will drop the database, recreate it,
restore using the backup over the new version, and fix the user access.
Sounds easy enough.
-- Mark D Powell --
Navigation:
[Reply to this message]
|