blocks|key|3095535|text|听起来备份是在一台路径与您的不匹配的机器上进行的。尝试使用T-SQL而不是UI执行备份。还要确保您指定的路径实际存在，并且其中没有这些mdf/ldf文件的副本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3095536|RESTORE+DATABASE+MYDB_ABC+FROM+DISK+=+'C:\path\file.bak'
WITH+MOVE+'mydb'+TO+'c:\valid_data_path\MYDB_ABC.mdf',
MOVE+'mydb_log'+TO+'c:\valid_log_path\MYDB_ABC.ldf';|code-block|syntax|javascript|3095537|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Sounds like the backup was taken on a machine whose paths do not match yours. Try performing the backup using T-SQL instead of the UI. Also make sure that the paths you're specifying actually exist and that there isn't already a copy of these mdf/ldf files in there.

<pre><code>RESTORE DATABASE MYDB_ABC FROM DISK = 'C:\path\file.bak'
WITH MOVE 'mydb' TO 'c:\valid_data_path\MYDB_ABC.mdf',
MOVE 'mydb_log' TO 'c:\valid_log_path\MYDB_ABC.ldf';
</code></pre>

blocks|key|227347|text|备份会存储数据库文件的原始位置，并且在默认情况下会尝试还原到相同的位置。由于您的新服务器安装在新目录中，并且假设旧目录不再存在，因此您需要更改默认目录，以匹配您希望它使用的位置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|227348|根据您恢复数据库的方式，执行此操作的方法会有所不同。如果您使用的是SSMS，请查看选项卡和列表，直到找到文件及其关联的磁盘位置的列表-然后可以在恢复之前编辑这些位置。|227349|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The backup stores the original location of the database files and, by default, attempts to restore to the same location. Since your new server installation is in new directories and, presumably, the old directories no longer exist, you need to alter the directories from the defaults to match the location you wish it to use.

Depending on how you are restoring the database, the way to do this will differ. If you're using SSMS, look through the tabs and lists until you find the list of files and their associated disk locations - you can then edit those locations before restoring.

blocks|key|223945|text|我已经设法从代码中做到了这一点。这还不够|type|unstyled|depth|inlineStyleRanges|entityRanges|data|223946|Restore+bkp+=+new+Restore();
bkp.PercentCompleteNotification+=+1;
bkp.Action+=+RestoreActionType.Database;
bkp.Database+=+sDatabase;
bkp.ReplaceDatabase+=+true;|code-block|syntax|javascript|223947|RelocateFiles属性必须填充要重新定位的文件的名称和路径。对于每个文件，必须指定文件名和新的物理路径。因此，我所做的是查看要恢复到的数据库的PrimaryFilePath，并将其用作物理位置。如下所示：|offset|length|style|CODE|223948|if+(!string.IsNullOrEmpty(sDataFileName)+&&+!File.Exists(sDataFileName))
{
+++if+(originaldb+!=+null)
+++{
++++++if+(string.Compare(Path.GetDirectoryName(sDataFileName),+originaldb.PrimaryFilePath,+true)+!=+0)
++++++{
+++++++++string+sPhysicalDataFileName+=+Path.Combine(originaldb.PrimaryFilePath,+sDatabase+%2B+".MDF");
+++++++++bkp.RelocateFiles.Add(new+RelocateFile(sLogicalDataFileName,+sPhysicalDataFileName));
++++++}++++++++++++++++++
+++}
}|223949|日志文件也是如此。|223950|entityMap^0|0|0|0|D|23|F|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]|$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

I have managed to do this from code. This was not enough 

<pre><code>Restore bkp = new Restore();
bkp.PercentCompleteNotification = 1;
bkp.Action = RestoreActionType.Database;
bkp.Database = sDatabase;
bkp.ReplaceDatabase = true;
</code></pre>

The <code>RelocateFiles</code> property must be filled with the names and paths of the files to be relocated. For each file you must specify the name of the file and the new physical path. So what I did was looking at the <code>PrimaryFilePath</code> of the database I was restoring to, and use that as the physical location. Something like this:

<pre><code>if (!string.IsNullOrEmpty(sDataFileName) &amp;&amp; !File.Exists(sDataFileName))
{
 if (originaldb != null)
 {
 if (string.Compare(Path.GetDirectoryName(sDataFileName), originaldb.PrimaryFilePath, true) != 0)
 {
 string sPhysicalDataFileName = Path.Combine(originaldb.PrimaryFilePath, sDatabase + ".MDF");
 bkp.RelocateFiles.Add(new RelocateFile(sLogicalDataFileName, sPhysicalDataFileName));
 } 
 }
}
</code></pre>

Same for the log file.

blocks|key|227368|text|请更改.mdf文件路径。只需在任何驱动器中创建一个文件夹，即在"D“驱动器中，只需创建一个具有自定义名称(dbase)的文件夹并指向新文件夹的路径，mssql将自动创建这些文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|227369|将"C:\PROGRAM+FILES\MICROSOFT+SQL+SERVER\MSSQL.1\MSSQL\DATA\MYDB_ABC.MDF“更改为"D:\dbase\MYDB_ABC.MDF”|227370|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Please change the .mdf file path. Just create a folder in any drive, ie - in "D" drive, just create a folder with custom name (dbase) and point the path to the new folder, mssql will automatically create the files.

"C:\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\DATA\MYDB_ABC.MDF"
to
"D:\dbase\MYDB_ABC.MDF"

blocks|key|226841|text|我也有同样的问题，不需要任何C#代码就可以解决这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|226842|USE+[master]
ALTER+DATABASE+[MyDb]+
SET+SINGLE_USER+WITH+ROLLBACK+IMMEDIATE
RESTORE+DATABASE+[MyDb]+
FROM++DISK+=+N'D:\backups\mydb.bak'+
WITH++FILE+=+1,++
MOVE+N'MyDb'+TO+N''c:\valid_data_path\MyDb.mdf',++
MOVE+N'MyDb_log'+TO+N'\valid_log_path\MyDb.ldf',++
NOUNLOAD,++
REPLACE,++
STATS+=+5
ALTER+DATABASE+[MyDb]+SET+MULTI_USER
GO|code-block|syntax|javascript|226843|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I had the same problem, and this fixed it without any C# code:

<pre class="lang-sql prettyprint-override"><code>USE [master]
ALTER DATABASE [MyDb] 
SET SINGLE_USER WITH ROLLBACK IMMEDIATE
RESTORE DATABASE [MyDb] 
FROM DISK = N'D:\backups\mydb.bak' 
WITH FILE = 1, 
MOVE N'MyDb' TO N''c:\valid_data_path\MyDb.mdf', 
MOVE N'MyDb_log' TO N'\valid_log_path\MyDb.ldf', 
NOUNLOAD, 
REPLACE, 
STATS = 5
ALTER DATABASE [MyDb] SET MULTI_USER
GO
</code></pre>

blocks|key|227387|text|请尝试取消选中[恢复数据库]对话框的[选项]页面上的[结尾日志备份]选项|type|unstyled|depth|inlineStyleRanges|entityRanges|data|227388|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Please try to uncheck the “Tail-Log Backup” option on the Options page of the Restore Database dialog

blocks|key|3095714|text|这里面有一些版本问题。你可以通过另外两种方法将你的数据库迁移到2012：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3095715|1)使数据库离线，然后将.mdf和.ldf文件复制到目标服务器数据文件夹，并附加数据库。请参阅：-+https://dba.stackexchange.com/questions/30440/how-do-i-attach-a-database-in-sql-server|offset|length|3095716|2)使用schema和Data创建整个数据库的脚本，并在目标服务器上运行它(非常慢的过程需要时间)。请参阅：-+Generate+script+in+SQL+Server+Management+Studio|3095717|entityMap|0|LINK|mutability|MUTABLE|url|https://dba.stackexchange.com/questions/30440/how-do-i-attach-a-database-in-sql-server|1|https://stackoverflow.com/questions/9429902/generate-script-in-sql-server-management-studio^0|0|1E|2E|0|0|1K|1B|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

There is some version issue in this. You can migrate your database to 2012 by 2 another methods:-

1) take the database offline > copy the .mdf and .ldf files to the target server data folder and attach the database. refer this:-
<a href="https://dba.stackexchange.com/questions/30440/how-do-i-attach-a-database-in-sql-server">https://dba.stackexchange.com/questions/30440/how-do-i-attach-a-database-in-sql-server</a>

2) Create script of the whole database with schema &amp; Data and run it on the target server(very slow process takes time). refer this:-
<a href="https://stackoverflow.com/questions/9429902/generate-script-in-sql-server-management-studio">Generate script in SQL Server Management Studio</a>

blocks|key|3095734|text|请尝试重新启动SQL服务。对我很管用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3095735|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try restarting the SQL Service. Worked for me.

blocks|key|226886|text|正如已经多次提到的，在mdf和ldf文件的新旧路径不匹配的情况下恢复备份可能会导致此错误。这里已经有几个很好的例子来说明如何使用SQL来处理这个问题，但是它们都没有对我起作用，直到我意识到在我的例子中，我需要在'MOVE‘语句的from部分中包括'.mdf’和'.ldf‘扩展，例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|226887|RESTORE+DATABASE+[SomeDB]+
FROM+DISK+=+N'D:\SomeDB.bak'+
WITH+MOVE+N'SomeDB.mdf'+TO+N'D:\SQL+Server\MSSQL12.MyInstance\MSSQL\DATA\SomeDB.mdf',+
MOVE+N'SomeDb_log.ldf'+TO+N'D:\SQL+Server\MSSQL12.MyInstance\MSSQL\DATA\SomeDB_log.ldf'|code-block|syntax|javascript|226888|我不明白为什么SQL建议我使用WITH+MOVE选项，而我已经在这么做了。|offset|length|style|CODE|226889|entityMap^0|0|0|F|9|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

As has already been said a few times, restoring a backup where the new and old paths for the mdf and ldf files don't match can cause this error. There are several good examples here already of how to deal with that with SQL, none of them however worked for me until I realised that in my case I needed to include the '.mdf' and '.ldf' extensions in the from part of the 'MOVE' statement, e.g.:

<pre><code>RESTORE DATABASE [SomeDB] 
FROM DISK = N'D:\SomeDB.bak' 
WITH MOVE N'SomeDB.mdf' TO N'D:\SQL Server\MSSQL12.MyInstance\MSSQL\DATA\SomeDB.mdf', 
MOVE N'SomeDb_log.ldf' TO N'D:\SQL Server\MSSQL12.MyInstance\MSSQL\DATA\SomeDB_log.ldf'
</code></pre>

Hope that saves someone some pain, I could not understand why SQL was suggesting I needed to use the <code>WITH MOVE</code> option when I already was doing so.

blocks|key|226913|text|恢复时，在文件下，选中‘将所有文件重新定位到文件夹’|type|unstyled|depth|inlineStyleRanges|entityRanges|data|226914|​|226915|📷|atomic|offset|length|226916|226917|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/c1433bdf219bca83bff5a216a32295f5.jpeg|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

When restoring, under Files, check 'Relocate all files to folder'

<a href="https://i.stack.imgur.com/ftciq.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/ftciq.jpg" alt="check &#39;Relocate all files to folder&#39;"></a>

blocks|key|229249|text|如果这对直接使用Powershell+(使用SMO库)的人有用，在这种特殊情况下，还有辅助数据文件。我通过杀死所有打开的进程，然后执行恢复，对脚本进行了一些改进。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|229250|Import-module+SQLPS
$svr+=+New-Object+("Microsoft.SqlServer.Management.Smo.Server")+"server+name";
$svr.KillAllProcesses("database_name");
$RelocateData1+=+New-Object+"Microsoft.SqlServer.Management.Smo.RelocateFile,+Microsoft.SqlServer.SmoExtended,+Version=13.0.0.0,+Culture=neutral,+PublicKeyToken=89845dcd8080cc91"+("primary_logical_name","C:\...\SQLDATA\DATA\database_name.mdf")
$RelocateData2+=+New-Object+"Microsoft.SqlServer.Management.Smo.RelocateFile,+Microsoft.SqlServer.SmoExtended,+Version=13.0.0.0,+Culture=neutral,+PublicKeyToken=89845dcd8080cc91"+("secondary_logical_name_2","C:\...\SQLDATA\DATA\secondary_file_2.mdf")
$RelocateData3+=+New-Object+"Microsoft.SqlServer.Management.Smo.RelocateFile,+Microsoft.SqlServer.SmoExtended,+Version=13.0.0.0,+Culture=neutral,+PublicKeyToken=89845dcd8080cc91"+("secondary_logical_name_3","C:\...\SQLDATA\DATA\secondary_file_3.mdf")
$RelocateLog+=+New-Object+"Microsoft.SqlServer.Management.Smo.RelocateFile,+Microsoft.SqlServer.SmoExtended,+Version=13.0.0.0,+Culture=neutral,+PublicKeyToken=89845dcd8080cc91"+("database_name_log","C:\...\SQLDATA\LOGS\database_name_log.ldf")
Restore-SqlDatabase+-ServerInstance+"server-name"+-Database+"database_name"+-BackupFile+"\\BACKUPS\\database_name.bak"+-RelocateFile+@($RelocateData1,+$RelocateData2,+$RelocateData3,+$RelocateLog)+-ReplaceDatabase|code-block|syntax|javascript|229251|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/sql/relational-databases/server-management-objects-smo/sql-server-management-objects-smo-programming-guide^0|M|3|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Just in case this is useful for someone working directly with Powershell (using the <a href="https://docs.microsoft.com/en-us/sql/relational-databases/server-management-objects-smo/sql-server-management-objects-smo-programming-guide" rel="nofollow noreferrer">SMO</a> library), in this particular case there were secondary data files as well. I enhanced the script a little by killing any open processes and then doing the restore. 

<pre><code>Import-module SQLPS
$svr = New-Object ("Microsoft.SqlServer.Management.Smo.Server") "server name";
$svr.KillAllProcesses("database_name");
$RelocateData1 = New-Object "Microsoft.SqlServer.Management.Smo.RelocateFile, Microsoft.SqlServer.SmoExtended, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" ("primary_logical_name","C:\...\SQLDATA\DATA\database_name.mdf")
$RelocateData2 = New-Object "Microsoft.SqlServer.Management.Smo.RelocateFile, Microsoft.SqlServer.SmoExtended, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" ("secondary_logical_name_2","C:\...\SQLDATA\DATA\secondary_file_2.mdf")
$RelocateData3 = New-Object "Microsoft.SqlServer.Management.Smo.RelocateFile, Microsoft.SqlServer.SmoExtended, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" ("secondary_logical_name_3","C:\...\SQLDATA\DATA\secondary_file_3.mdf")
$RelocateLog = New-Object "Microsoft.SqlServer.Management.Smo.RelocateFile, Microsoft.SqlServer.SmoExtended, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" ("database_name_log","C:\...\SQLDATA\LOGS\database_name_log.ldf")
Restore-SqlDatabase -ServerInstance "server-name" -Database "database_name" -BackupFile "\\BACKUPS\\database_name.bak" -RelocateFile @($RelocateData1, $RelocateData2, $RelocateData3, $RelocateLog) -ReplaceDatabase
</code></pre>

blocks|key|2881849|text|您应该从脚本中删除这些行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2881850|CONTAINMENT+=+NONE
+ON++PRIMARY+
(+NAME+=+N'StudentManagement',+FILENAME+=+N'C:\Program+Files\Microsoft+SQL+Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\StudentManagement.mdf'+,+SIZE+=+10240KB+,+MAXSIZE+=+UNLIMITED,+FILEGROWTH+=+1024KB+)
+LOG+ON+
(+NAME+=+N'StudentManagement_log',+FILENAME+=+N'C:\Program+Files\Microsoft+SQL+Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\StudentManagement_log.ldf'+,+SIZE+=+5696KB+,+MAXSIZE+=+2048GB+,+FILEGROWTH+=+10%25)
GO
ALTER+DATABASE+[StudentManagement]+SET+COMPATIBILITY_LEVEL+=+110
GO
IF+(1+=+FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'))
begin
EXEC+[StudentManagement].[dbo].[sp_fulltext_database]+@action+=+'enable'
end
GO
ALTER+DATABASE+[StudentManagement]+SET+ANSI_NULL_DEFAULT+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+ANSI_NULLS+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+ANSI_PADDING+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+ANSI_WARNINGS+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+ARITHABORT+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+AUTO_CLOSE+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+AUTO_CREATE_STATISTICS+ON+
GO
ALTER+DATABASE+[StudentManagement]+SET+AUTO_SHRINK+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+AUTO_UPDATE_STATISTICS+ON+
GO
ALTER+DATABASE+[StudentManagement]+SET+CURSOR_CLOSE_ON_COMMIT+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+CURSOR_DEFAULT++GLOBAL+
GO
ALTER+DATABASE+[StudentManagement]+SET+CONCAT_NULL_YIELDS_NULL+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+NUMERIC_ROUNDABORT+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+QUOTED_IDENTIFIER+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+RECURSIVE_TRIGGERS+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET++DISABLE_BROKER+
GO
ALTER+DATABASE+[StudentManagement]+SET+AUTO_UPDATE_STATISTICS_ASYNC+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+DATE_CORRELATION_OPTIMIZATION+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+TRUSTWORTHY+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+ALLOW_SNAPSHOT_ISOLATION+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+PARAMETERIZATION+SIMPLE+
GO
ALTER+DATABASE+[StudentManagement]+SET+READ_COMMITTED_SNAPSHOT+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+HONOR_BROKER_PRIORITY+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+RECOVERY+SIMPLE+
GO
ALTER+DATABASE+[StudentManagement]+SET++MULTI_USER+
GO
ALTER+DATABASE+[StudentManagement]+SET+PAGE_VERIFY+CHECKSUM++
GO
ALTER+DATABASE+[StudentManagement]+SET+DB_CHAINING+OFF+
GO
ALTER+DATABASE+[StudentManagement]+SET+FILESTREAM(+NON_TRANSACTED_ACCESS+=+OFF+)+
GO
ALTER+DATABASE+[StudentManagement]+SET+TARGET_RECOVERY_TIME+=+0+SECONDS+|code-block|syntax|javascript|2881851|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You should remove these lines from your script.

<pre><code>CONTAINMENT = NONE
 ON PRIMARY 
( NAME = N'StudentManagement', FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\StudentManagement.mdf' , SIZE = 10240KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB )
 LOG ON 
( NAME = N'StudentManagement_log', FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\StudentManagement_log.ldf' , SIZE = 5696KB , MAXSIZE = 2048GB , FILEGROWTH = 10%)
GO
ALTER DATABASE [StudentManagement] SET COMPATIBILITY_LEVEL = 110
GO
IF (1 = FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'))
begin
EXEC [StudentManagement].[dbo].[sp_fulltext_database] @action = 'enable'
end
GO
ALTER DATABASE [StudentManagement] SET ANSI_NULL_DEFAULT OFF 
GO
ALTER DATABASE [StudentManagement] SET ANSI_NULLS OFF 
GO
ALTER DATABASE [StudentManagement] SET ANSI_PADDING OFF 
GO
ALTER DATABASE [StudentManagement] SET ANSI_WARNINGS OFF 
GO
ALTER DATABASE [StudentManagement] SET ARITHABORT OFF 
GO
ALTER DATABASE [StudentManagement] SET AUTO_CLOSE OFF 
GO
ALTER DATABASE [StudentManagement] SET AUTO_CREATE_STATISTICS ON 
GO
ALTER DATABASE [StudentManagement] SET AUTO_SHRINK OFF 
GO
ALTER DATABASE [StudentManagement] SET AUTO_UPDATE_STATISTICS ON 
GO
ALTER DATABASE [StudentManagement] SET CURSOR_CLOSE_ON_COMMIT OFF 
GO
ALTER DATABASE [StudentManagement] SET CURSOR_DEFAULT GLOBAL 
GO
ALTER DATABASE [StudentManagement] SET CONCAT_NULL_YIELDS_NULL OFF 
GO
ALTER DATABASE [StudentManagement] SET NUMERIC_ROUNDABORT OFF 
GO
ALTER DATABASE [StudentManagement] SET QUOTED_IDENTIFIER OFF 
GO
ALTER DATABASE [StudentManagement] SET RECURSIVE_TRIGGERS OFF 
GO
ALTER DATABASE [StudentManagement] SET DISABLE_BROKER 
GO
ALTER DATABASE [StudentManagement] SET AUTO_UPDATE_STATISTICS_ASYNC OFF 
GO
ALTER DATABASE [StudentManagement] SET DATE_CORRELATION_OPTIMIZATION OFF 
GO
ALTER DATABASE [StudentManagement] SET TRUSTWORTHY OFF 
GO
ALTER DATABASE [StudentManagement] SET ALLOW_SNAPSHOT_ISOLATION OFF 
GO
ALTER DATABASE [StudentManagement] SET PARAMETERIZATION SIMPLE 
GO
ALTER DATABASE [StudentManagement] SET READ_COMMITTED_SNAPSHOT OFF 
GO
ALTER DATABASE [StudentManagement] SET HONOR_BROKER_PRIORITY OFF 
GO
ALTER DATABASE [StudentManagement] SET RECOVERY SIMPLE 
GO
ALTER DATABASE [StudentManagement] SET MULTI_USER 
GO
ALTER DATABASE [StudentManagement] SET PAGE_VERIFY CHECKSUM 
GO
ALTER DATABASE [StudentManagement] SET DB_CHAINING OFF 
GO
ALTER DATABASE [StudentManagement] SET FILESTREAM( NON_TRANSACTED_ACCESS = OFF ) 
GO
ALTER DATABASE [StudentManagement] SET TARGET_RECOVERY_TIME = 0 SECONDS 
</code></pre>

blocks|key|3095888|text|当您使用一个MSSQL+Studio进行备份(连接到旧服务器)和还原(连接到新服务器)时，通常会发生这种情况。只需确保在正确的服务器上执行恢复即可。在UI或dou的左窗格中检查服务器名称和IP|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3095889|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This usually happens, when you are using one MSSQL Studio for backup (connected to old server) and restore (connected to new one). Just make sure you are executing the restore on the correct server. Either check the server name and IP in the left pane in UI or dou

blocks|key|224084|text|如果您使用C#执行此操作，并且物理路径不同，则需要使用RelocateFiles，因为这里也提到了一个答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|224085|在大多数情况下，假设以下代码可以工作：|224086|224087|您只是在从其他地方恢复数据库的备份，否则将是相同的。例如，将产品的副本复制到本地Db。|ordered-list-item|224088|您没有使用非典型的数据库布局，例如，rows文件分布在多个磁盘上的多个文件中。|224089|224090|此外，只有在第一次恢复时才需要执行以下操作。一旦成功进行了一次恢复，就已经在Sql+Server中设置了以下文件映射。但是，在第一次将bak文件恢复到空白数据库时，您基本上必须说，“是的，在默认的本地位置使用db文件，而不是抓狂”，并且您需要告诉它将东西放在相同的位置，奇怪的是，告诉它重新定位它们：|224091|var+dbDataFile+=+db.FileGroups[0].Files[0];
restore.RelocateFiles.Add(new+RelocateFile(dbDataFile.Name,+dbDataFile.FileName));
var+dbLogFile+=+db.LogFiles[0];
restore.RelocateFiles.Add(new+RelocateFile(dbLogFile.Name,+dbLogFile.FileName));|code-block|syntax|javascript|224092|为了更好地阐明典型情况，以及如何执行还原，以下是将.bak文件典型还原到本地计算机的完整代码：|224093|var+smoServer+=+new+Microsoft.SqlServer.Management.Smo.Server(
++++new+Microsoft.SqlServer.Management.Common.ServerConnection(sqlServerInstanceName));

var+db+=+smoServer.Databases[dbName];
if+(db+==+null)
{
++++db+=+new+Microsoft.SqlServer.Management.Smo.Database(smoServer,+dbName);
++++db.Create();
}

restore.Devices.AddDevice(backupFileName,+DeviceType.File);
restore.Database+=+dbName;
restore.FileNumber+=+0;
restore.Action+=+RestoreActionType.Database;
restore.ReplaceDatabase+=+true;

var+dbDataFile+=+db.FileGroups[0].Files[0];
restore.RelocateFiles.Add(new+RelocateFile(dbDataFile.Name,+dbDataFile.FileName));
var+dbLogFile+=+db.LogFiles[0];
restore.RelocateFiles.Add(new+RelocateFile(dbLogFile.Name,+dbLogFile.FileName));

restore.SqlRestore(smoServer);

db.SetOnline();
smoServer.Refresh();
db.Refresh();|224094|无论您以前是否手动恢复过此数据库，是手动创建了一个只有名称而没有数据的数据库，还是什么都不做-从一台完全空白的计算机启动，只安装了Sql+Server，而没有任何数据库，这些代码都可以正常工作。|224095|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|12|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|13|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|15|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|16|8|@]|9|@]|A|$P|Q]]|$1|R|3|S|5|6|7|17|8|@]|9|@]|A|$]]|$1|T|3|U|5|O|7|18|8|@]|9|@]|A|$P|Q]]|$1|V|3|W|5|6|7|19|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|Y|$]]

If you're doing this with C#, and the physical paths are not the same, you need to use RelocateFiles, as one answer here also mentioned.

For most cases, the below code will work, assuming:

<ol>
<li>You're just restoring a backup of a database from elsewhere, otherwise meant to be identical. For example, a copy of production to a local Db.</li>
<li>You aren't using an atypical database layout, for example one where the rows files are spread across multiple files on multiple disks.</li>
</ol>

In addition, the below is only necessary on first restore. Once a single successful restore occurs, the below file mapping will already be setup for you in Sql Server. But, the first time - restoring a bak file to a blank db - you basically have to say, "Yes, use the Db files in their default, local locations, instead of freaking out" and you need to tell it to keep things in the same place by, oddly enough, telling it to relocate them:

<pre><code>var dbDataFile = db.FileGroups[0].Files[0];
restore.RelocateFiles.Add(new RelocateFile(dbDataFile.Name, dbDataFile.FileName));
var dbLogFile = db.LogFiles[0];
restore.RelocateFiles.Add(new RelocateFile(dbLogFile.Name, dbLogFile.FileName));
</code></pre>

To better clarify what a typical case would be, and how you'd do the restore, here's the full code for a typical restore of a .bak file to a local machine:

<pre><code>var smoServer = new Microsoft.SqlServer.Management.Smo.Server(
 new Microsoft.SqlServer.Management.Common.ServerConnection(sqlServerInstanceName));

var db = smoServer.Databases[dbName];
if (db == null)
{
 db = new Microsoft.SqlServer.Management.Smo.Database(smoServer, dbName);
 db.Create();
}

restore.Devices.AddDevice(backupFileName, DeviceType.File);
restore.Database = dbName;
restore.FileNumber = 0;
restore.Action = RestoreActionType.Database;
restore.ReplaceDatabase = true;

var dbDataFile = db.FileGroups[0].Files[0];
restore.RelocateFiles.Add(new RelocateFile(dbDataFile.Name, dbDataFile.FileName));
var dbLogFile = db.LogFiles[0];
restore.RelocateFiles.Add(new RelocateFile(dbLogFile.Name, dbLogFile.FileName));

restore.SqlRestore(smoServer);

db.SetOnline();
smoServer.Refresh();
db.Refresh();
</code></pre>

This code will work whether you've manually restored this Db before, created one manually with just the name and no data, or done nothing - started with a totally blank machine, with just Sql Server installed and no databases whatsoever.

I am getting an error using SQL Server 2012 when restoring a backup made with a previous version (SQL Server 2008). I actually have several backup files of the same database (taken at different times in the past). The newest ones are restored without any problems; however, one of them gives the following error:

<blockquote>
 System.Data.SqlClient.SqlError: Directory lookup for the file
 "C:\PROGRAM FILES\MICROSOFT SQL
 SERVER\MSSQL.1\MSSQL\DATA\MYDB_ABC.MDF" failed with the operating
 system error 3(The system cannot find the path specified.).
 (Microsoft.SqlServer.SmoExtended)
</blockquote>

This is a x64 machine, and my database file(s) are in this location: <code>c:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL</code>.

I do not understand why it tries to restore on <code>MSSQL.1</code> and not <code>MSSQL11.MSSQLSERVER</code>.

Error restoring database backup

日志文件

SQL Server

数据库

服务器

在恢复使用以前版本(SQL Server 2008)创建的备份时，我在使用SQL Server 2012时出错。实际上，我有同一数据库的几个备份文件(在过去的不同时间拍摄)。恢复最新的文件时没有任何问题；但是，其中一个文件会显示以下错误： System.Data.SqlClient.SqlError:文件"C:\PRO...

问还原数据库备份时出错
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问还原数据库备份时出错EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问还原数据库备份时出错
EN