Results 1 to 2 of 2
  1. #1
    Join Date
    Nov 2004
    Posts
    1,427
    Provided Answers: 4

    Unanswered: Problem with database copy

    I tried to make a copy of an online database. In MSSQL Server Management Studio 2005, I right clicked the source database Tasks | Copy database ... | Use the SQL Management Object method | ...

    The process starts and in the final 5th step "Exceute SQL Server Agent Job", it stops with an error message:

    "The job failed. Check the event log on the destination server for details."

    I checked the ERRORLOG event log.

    2010-08-27 10:15:01.04 spid23s Changing the status to MERGE for full-text catalog "ftcat_documentindex" (5) in database "DatabaseName" (7). This is an informational message only. No user action is required.
    2010-08-27 10:15:43.45 spid54 Starting up database 'Test_DatabaseName'.
    2010-08-27 10:15:43.53 spid54 Analysis of database 'Test_DatabaseName' (10) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
    2010-08-27 10:15:44.94 spid54 Setting database option ANSI_NULL_DEFAULT to OFF for database Test_DatabaseName.
    2010-08-27 10:15:44.95 spid54 Setting database option ANSI_NULLS to OFF for database Test_DatabaseName.
    2010-08-27 10:15:44.96 spid54 Setting database option ANSI_PADDING to OFF for database Test_DatabaseName.
    2010-08-27 10:15:44.96 spid54 Setting database option ANSI_WARNINGS to OFF for database Test_DatabaseName.
    2010-08-27 10:15:44.98 spid54 Setting database option ARITHABORT to OFF for database Test_DatabaseName.
    2010-08-27 10:15:44.99 spid54 Setting database option AUTO_CLOSE to OFF for database Test_DatabaseName.
    2010-08-27 10:15:45.00 spid54 Setting database option AUTO_CREATE_STATISTICS to ON for database Test_DatabaseName.
    2010-08-27 10:15:45.00 spid54 Setting database option AUTO_SHRINK to OFF for database Test_DatabaseName.
    2010-08-27 10:15:45.01 spid54 Setting database option AUTO_UPDATE_STATISTICS to ON for database Test_DatabaseName.
    2010-08-27 10:15:45.01 spid54 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database Test_DatabaseName.
    2010-08-27 10:15:45.02 spid54 Setting database option CURSOR_DEFAULT to GLOBAL for database Test_DatabaseName.
    2010-08-27 10:15:45.03 spid54 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database Test_DatabaseName.
    2010-08-27 10:15:45.04 spid54 Setting database option NUMERIC_ROUNDABORT to OFF for database Test_DatabaseName.
    2010-08-27 10:15:45.05 spid54 Setting database option QUOTED_IDENTIFIER to OFF for database Test_DatabaseName.
    2010-08-27 10:15:45.05 spid54 Setting database option RECURSIVE_TRIGGERS to OFF for database Test_DatabaseName.
    2010-08-27 10:15:45.06 spid54 Setting database option ENABLE_BROKER to ON for database Test_DatabaseName.
    2010-08-27 10:15:45.06 spid54 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database Test_DatabaseName.
    2010-08-27 10:15:45.07 spid54 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database Test_DatabaseName.
    2010-08-27 10:15:45.07 spid54 Setting database option TRUSTWORTHY to OFF for database Test_DatabaseName.
    2010-08-27 10:15:45.08 spid54 Setting database option ALLOW_SNAPSHOT_ISOLATION to OFF for database Test_DatabaseName.
    2010-08-27 10:15:45.09 spid54 Setting database option PARAMETERIZATION to SIMPLE for database Test_DatabaseName.
    2010-08-27 10:15:45.09 spid54 Setting database option READ_WRITE to ON for database Test_DatabaseName.
    2010-08-27 10:15:45.10 spid54 Setting database option RECOVERY to SIMPLE for database Test_DatabaseName.
    2010-08-27 10:15:45.11 spid54 Setting database option MULTI_USER to ON for database Test_DatabaseName.
    2010-08-27 10:15:45.11 spid54 Setting database option PAGE_VERIFY to CHECKSUM for database Test_DatabaseName.
    2010-08-27 10:15:45.12 spid54 Setting database option DB_CHAINING to OFF for database Test_DatabaseName.
    2010-08-27 10:30:00.53 spid26s Changing the status to MERGE for full-text catalog "ftcat_documentindex" (5) in database "DatabaseName" (7). This is an informational message only. No user action is required.

    I can see no error message. What could be the cause of the failed database copy? Any better way?
    Last edited by Wim; 08-27-10 at 07:30. Reason: Added MSSQL version
    With kind regards . . . . . SQL Server 2000/2005/2012
    Wim

    Grabel's Law: 2 is not equal to 3 -- not even for very large values of 2.
    Pat Phelan's Law: 2 very definitely CAN equal 3 -- in at least two programming languages

  2. #2
    Join Date
    Jan 2009
    Location
    United Kingdom
    Posts
    77
    Try :
    1)Backup \ Restore
    2)Detach \ Attach

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •