Attaches a database that has only one data file to the current server. sp_attach_single_file_db cannot be used with multiple data files.
This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. We recommend that you use CREATE DATABASE database_name FOR ATTACH instead. For more information, see CREATE DATABASE (Transact-SQL). Do not use this procedure on a replicated database.
We recommend that you do not attach or restore databases from unknown or untrusted sources. Such databases could contain malicious code that might execute unintended Transact-SQL code or cause errors by modifying the schema or the physical database structure. Before you use a database from an unknown or untrusted source, run DBCC CHECKDB on the database on a nonproduction server and also examine the code, such as stored procedures or other user-defined code, in the database.
Use sp_attach_single_file_db only on databases that were previously detached from the server by using an explicit sp_detach_db operation or on copied databases.
sp_attach_single_file_db works only on databases that have a single log file. When sp_attach_single_file_db attaches the database to the server, it builds a new log file. If the database is read-only, the log file is built in its previous location.
A database snapshot cannot be detached or attached.
Do not use this procedure on a replicated database.
For information about how permissions are handled when a database is attached, see CREATE DATABASE (Transact-SQL).
The following example detaches AdventureWorks2012 and then attaches one file from AdventureWorks2012 to the current server.
USE master; GO EXEC sp_detach_db @dbname = 'AdventureWorks2012'; EXEC sp_attach_single_file_db @dbname = 'AdventureWorks2012', @physname = N'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Data\AdventureWorks2012_Data.mdf';