Post reply

DTS and MSDB Questions

  • August 16, 2007 at 12:16 pm

    #178119

    Long story but a vendor dropped and reattached my databases but did not reattach the MSDB database. As a result all (about 40) of my DTS packages are missing and I don't have a current backup (no flaming please). So my questions are:

    1. Can I drop my current MSDB and attach my old MSDB without creating a new problem?

    2. Alternatively could I rename the old MSDB attach it and copy the rows from sysdtspackages in the renamed MSDB to the current MSDB?

    3. Do you have a better suggestion?

    TIA

    Ken

  • August 16, 2007 at 2:28 pm

    #727495

    I think you can detach the current MSDB database, move the database files of the old database and reattach.

    See this article: http://support.microsoft.com/kb/224071/

    Greg

    Greg

  • August 18, 2007 at 11:34 pm

    #727860

    Unfortunately I got stuck at the second step where I detach msdb. Since I think I followed the first step exactly as laid out by Microsoft I will give them a call tomorrow and see if they can help me. Wish me luck!

  • August 19, 2007 at 12:30 am

    #727863

    Heh... ok... no flaming   But I'll just bet you'll never again let another vendor touch your DB's without making a full backup, huh?   I learned that lesson the same way

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
    "Change is inevitable... change for the better is not".
    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)
    Intro to Tally Tables and Functions

  • August 20, 2007 at 9:30 am

    #728017

    I have a product for you. I ran into this when I was Moving DB's from one server to another. http://www.sqldts.com/242.aspx DTSBackup2000 Works great for moving jobs between or just backing them up so you can recover them. Reattach the old DB then run this to backup your old jobs. then drop and attach the new one, recover your old DTS jobs and life is good once again.

  • August 20, 2007 at 10:01 am

    #728035

    Great, I'll try it!

  • August 20, 2007 at 10:01 am

    #728034

    You got that right!

  • October 23, 2007 at 5:35 am

    #744440

    Kenneth Gladden (8/16/2007)

    Long story but a vendor dropped and reattached my databases but did not reattach the MSDB database. As a result all (about 40) of my DTS packages are missing

    Best to detach the "new" msdb and reattach the "old" msdb mdf and ldf files in it's place - because it won't be just your DTS packages you have lost - also things like SQL scheduled jobs, backup hsitory etc are held in msdb

    James Horsley
    Workflow Consulting Limited

  • October 23, 2007 at 5:42 am

    #744442

    even i'm not sure whether this work. Just by dropping & attaching the respective objects into the server might tamper the operational behaviour too.. Better try the same in a stand-alone machine then replicate the similar process on the main server.

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

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