Moving User Tables

  • I plan on moving my user table to a larger hard drive.  What is the best method?  Can I just do a backup of the user table and log file, then detach, then restore with the move option?  And only do this for the user table?  Can I just leave the master db alone?

    Thanks,

    Brian

  • Backup and restore (with the move option) of the user "databases" will work fine.  The system databases (master, model, msdb and tempdb) can be left as is if you do not anticipate too much growth and if the existing logical drive that those are on has enough space.  If the application uses tempdb a lot, then you should consider moving that as well.

  • Can you tell me how to check if the tempdb is used alot?  I didn't program the application using this db, so I don't know if it uses that table alot.  I am just assuming that it does not.

    Brian

  • You can't backup tempDB so don't worry about it.  If your database makes heavy use of tempdb you should just make sure that you replicate its configuration on the second server (multiple files, seperate drives).  Databases that make heavy use of tempdb are databases that contain stored procedures with lots of temp tables (any table name that starts with a #).  Many other SQL Server operations make use of tempdb as well such as certain indexing tasks. 

  • To move the database Backup DB --> Copy-->Restore DB

    with move option is safe practise.

    Better avoid temptation of detach & attach db option.This is last available option not the preferrred one.

    You can get proof to my opinion from microsoft's link for depricated features in Sql 2005. Attach_db is depricated feature in 2005.

    Hope this helps

     

    Kindest Regards,

    Sameer Raval [Sql Server DBA]
    Geico Insurance
    RavalSameer@hotmail.com

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply