Can I restore part of the database to a mapped drive due to disk space issue ?

  • Hi

    I have a backup file in a portable hard drive directly attached to the server ( one that has Sql sever )

    I am going to do a restore using the following command:

    restore database NGDEVL

    from disk = N'R:\NGDVLBK12032010' -- assumes the file is local - Ask Dave for the path of the file.

    with file = 1,

    move 'NextGen_System_Data' to 'M:\SQL Data Files DBI02\MSSQL.4\MSSQL\Data\NGDevl_System_Data.mdf',

    move 'NextGen_Core_Data_1' to 'X:\Data\NGDevl_Core_Data_1.ndf',

    move 'NextGen_Index_1' to 'M:\SQL Data Files DBI02\MSSQL.4\MSSQL\Data\NGDevl_Index_1.ndf',

    move 'NextGen_Log' to 'N:\SQL Log Files DBI02\NGDevl_Log.ldf',

    recovery,

    stats = 10;

    Points to note:

    R: points to the drive letter assigned to the portable hard drive.

    M: refers to the drive that has Sql server.

    x: refers to a mapped drive in another server.

    Here is my question:

    Will the RESTORE work with mapped drives ( where the actual drive sits in another server )

  • No. SQL has a number of requirements for drives for data files, the network protocol doesn't meet them.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Using SQL Virtual Restore[/url] may be another option if space is limited. Basically, you can mount live databases from backup sets without actually having to restore the original data and log files.

    SQL BAK Explorer - read SQL Server backup file details without SQL Server.
    Supports backup files created with SQL Server 2005 up to SQL Server 2017.

  • SQL Server can be configured using a trace flag to allow the use of network drives. Trace flag 1807 bypasses SQL Servers checks for network bases drive.

    There are reasons that Microsoft implemented the standard checks that normally stop you using network drives for database files. These are because SQL Server is expected disk drives to, for instances, actually garentee that data is written when the drive (and associated firmware etc) says that data has been written. You run the risk of corruption occurring in you database if you do use network drives.

    For more information, have a read of http://support.microsoft.com/kb/304261. It discusses the issues and you can then make an informed decision on whether to use this trace flag.

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

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