Results 1 to 8 of 8
  1. #1
    Join Date
    Jun 2007

    Unanswered: I have a crazy question!!! (Possible or Un-Possible?)

    Let me please start off by saying if your response to this question is:

    "That's retarded! Why are you doing it that way! Do it this way!"

    Please refrain from answering my query. With that out of the way, here I go.

    I have attached a Sql Server 7.0 db (.mdf and .ldf file) to an instance of MSSQL 2000. When this attach happens, MSSQL2000 automatically upgrades it.

    I then detach the db, and place the modified files back into the directory the Server 7.0 instance looks for. Obviously the format of the db files (.mdf and .ldf) have changed following the upgrade. I need to know if there is anything I can do (script or programmatically) to modify the files so that my Sql Server 7.0 instance can read them properly when the engine goes online.

    Thank you in advance for any tidbits you can provide

  2. #2
    Join Date
    Nov 2004
    on the wrong server
    Provided Answers: 6
    as far as I know there is no downgrade procedure.
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

  3. #3
    Join Date
    Jan 2003
    Provided Answers: 17
    As Thrasymachus said, there is no downgrade procedure. in order to get the data back to the 7.0 machine, you will need to export the data from SQL 2000, and import it back to the 7.0 server. DTS can export the data directly to the 7.0 database, but the stored procedures, users, permissions, etc. will have to be scripted.

  4. #4
    Join Date
    Jun 2003
    Provided Answers: 1
    Quote Originally Posted by rationalBean
    Let me please start off by saying if your response to this question is:

    "That's retarded! Why are you doing it that way! Do it this way!"

    Please refrain from answering my query.
    Eh....I've seen worse....
    If it's not practically useful, then it's practically useless.

    blindman "sqlblindman"

  5. #5
    Join Date
    Feb 2004
    In front of the computer
    Provided Answers: 54
    There is no automated or Microsoft supported way to migrate a database from SQL 2000 back to SQL 7.

    There are a number of ways that you can do it, they just aren't automated or supported by Microsoft. Some of these ways are relatively simple, but all of the ways that I know need at least a "helper" instance of SQL 2000.

    Would it be acceptable to leave the database running on SQL 2000 (or better yet SQL 2005) and simply set the database compatibility level to SQL 7? This gets you the syntax and behavior that SQL 7 had, but on a supportable product. SQL 7 has been in "Extended Support" for over two years, so reverting back to it now is a very questionable business decision.


  6. #6
    Join Date
    Jun 2004
    Long Island
    Can you backup/restore instead of detach/attach ?

  7. #7
    Join Date
    Dec 2007
    London, UK
    Quote Originally Posted by PMASchmed
    Can you backup/restore instead of detach/attach ?
    No. You can't restore to an earlier version.

  8. #8
    Join Date
    Nov 2002
    Just curious though, can you explain the process model as why you need to do this?

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

Posting Permissions

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