Re: Restoring DB**

From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 12/18/04 

Date: Sat, 18 Dec 2004 09:14:07 -0500

It sounds like the location of where the files were on the original machine
are different than the one you are restoring to. If that is the cases you
must use the WITH MOVE option to specify a new location. If your log file
is 6GB and your db is only 450MB you are not doing backups properly. You
must issue regular log backups if you are in FULL recovery mode, otherwise
set it to SIMPLE. That will keep the log file from growing. These will hep
you get it back to normal size.

http://www.nigelrivett.net/TransactionLogFileGrows_1.html Log File issues
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
http://www.support.microsoft.com/?id=256650 INF: How to Shrink the SQL
Server 7.0 Tran Log
http://www.support.microsoft.com/?id=272318 INF: Shrinking Log in SQL
Server 2000 with DBCC SHRINKFILE
http://www.karaszi.com/SQLServer/info_dont_shrink.asp Shrinking
considerations 

-- 
Andrew J. Kelly  SQL MVP
"maryam rezvani" <rezvani@parskhazar.net> wrote in message 
news:ODYGgTM5EHA.2180@TK2MSFTNGP12.phx.gbl...
> Hi
>
> I restore my db backup in different station by following the same steps 
> .but
> in some of
> them it restores successfully and in the others folowing error appearred.
> (my db is in
> full recovery model and it's backup size is about 450mg and it's .mdf and
> .ldf files
> are about 450mg and 6gig in order)
>
> error:
> "modify file encountered operationg system error 112 (error not found) 
> while
> attemting
> to exapand the physical file. could not create one or more files.consider
> using the
> with move option to modify while location restore database is terminating
> abnormally."
>
> I checked the destination if it's correct or not and the enough 
> space(about
> 10gig is
> free on destination drive) but still above error happenned.any help would 
> be
> greatly
> thankful.
>
>
>
>

Relevant Pages

  • Re: how often autoshrink?
    ... Autoshrink is not a very good option to enable, ... attack the log file. ... because under typical usage the file will shrink then you will need it to ... For databases that are not mission critical (e.g. full backups, ...
    (microsoft.public.sqlserver.programming)
  • Re: Backup/Restore File groups
    ... your backups down to 70 or 80%. ... > avoiding the log file to grow. ... to be able to restore one filegroup. ...
    (microsoft.public.sqlserver.tools)
  • Re: Log Shipping....
    ... Log files never shrink unless you issue a shrink command or have the ... If you issue regualr log backups and don't have ... long running open transactions the log file can reuse the parts of the log ...
    (microsoft.public.sqlserver.clients)
  • Re: Exact use of Log file - why so big?
    ... cross between DB and CSV/SVN in a way...), and do incremental backups ... SIMPLE means restore only to full backup ... BULK-LOGGED is sort of between the two... ... The log file will grow between backups... ...
    (microsoft.public.sqlserver.setup)
  • Re: HELP!! Transaction Log is huge
    ... > translog backup, and truncate after. ... > Then shrink the log file. ... During the restore I moved the ...
    (microsoft.public.sqlserver.server)