Post reply

Copying database error

  • November 4, 2013 at 3:29 am

    #279548

    HI Experts

    I am trying to copy a database on the same server but the error says the job is failed check event log, the event log says

    "SQL Server Scheduled Job 'copy-db' (0x6A43FA432AD02D44BCADB266A986DA85) - Status: Failed - Invoked on: 2013-11-04 12:10:36 - Message: The job failed. The Job was invoked by User Hassan\Dell. The last step to run was step 1 (copy-db_Step)."

    any advise how to success this job

    Thanks lot

  • November 4, 2013 at 3:44 am

    #1663761

    Is there some more details available on ther server?

    Can you check the job history and see the error details?

    Regards
    Durai Nagarajan

  • November 4, 2013 at 3:48 am

    #1663763

    If you want to make a copy of the DB, why not just take a backup and restore the backup as a new database?

    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

  • November 4, 2013 at 3:56 am

    #1663764

    I want to schedule recurring copying database from production to test

  • November 4, 2013 at 4:08 am

    #1663767

    Why not use backup/restore? Far less hassle than a copy job, much less impact on production (you can just use the previous night's production backup) and probably faster.

    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

  • November 4, 2013 at 7:02 am

    #1663799

    Without more details, I can't tell you what's wrong.

    I'm with Gail though. Use backup and restore. Doing that will not only get you your copy of of the database, but you'll also be validating your backups by running a restore process against them. That kills two birds with one stone, always a win.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • November 5, 2013 at 3:57 am

    #1664082

    I just want an automated process, that's why I thought about using copy db

  • November 5, 2013 at 4:11 am

    #1664087

    Copying and restoring a backup can be automated probably easier than copying, plus all the other advantages of restoring a backup that have been mentioned.

    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

  • November 5, 2013 at 8:33 pm

    #1664314

    zi (11/5/2013)

    I just want an automated process, that's why I thought about using copy db

    Why dont you use replication but you cant alter any data..

    Can you give us the purpose of syncing it on "X" no of days?

    Regards
    Durai Nagarajan

Viewing 9 posts - 1 through 8 (of 8 total)

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