1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Resolved How do I move a pervasive.SQL v8 database to pervasive.SQL ver11

Discussion in 'Other PC Software' started by mfctome, 2012/01/12.

  1. 2012/01/12
    mfctome

    mfctome Inactive Thread Starter

    Joined:
    2011/01/20
    Messages:
    7
    Likes Received:
    0
    I have an old server running Windows Server 2000 (32 bit) with a dbms called pervasive.SQL ver8. (32 bit) I want to move this database to a server running Windows Server 2008 r2 (64 bit) and pervasive.SQL ver11 (64 bit) Is it possible to just install the pervasive.SQL ver11 and then migrate all the data by running a backup restore from the old pervasive.SQL ver8? If not, does anyone have any ideas on how to accomplish this task? Thank you.
     
    mfctome,
    #1
  2. 2012/02/17
    mfctome

    mfctome Inactive Thread Starter

    Joined:
    2011/01/20
    Messages:
    7
    Likes Received:
    0
    Still no reply to this post. I patiently await a solution.
     
    mfctome,
    #2


  3. to hide this advert.

  4. 2012/02/17
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    I don't know any of our 'regulars' that would be proficient with SQL.

    Now, I can use a search engine, so come up with: How to move databases between computers that are running SQL Server

    And: Moving data between 32-bit and 64-bit SQL Server instances

    Don't know if you'd experience any problem going from v8 to v11... I would think not (you are 'upgrading'. Going back couldbe a problem). I would just try & see ;)
     
    Arie,
    #3
    mfctome likes this.
  5. 2012/02/18
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    Usually what happens when changing database servers is that queries used in old versions break due to updates and changes in the query language. Databases themselves don't suffer.
     
    TonyT,
    #4
    mfctome likes this.
  6. 2012/02/18
    mfctome

    mfctome Inactive Thread Starter

    Joined:
    2011/01/20
    Messages:
    7
    Likes Received:
    0
    Thank yall very much!
     
    mfctome,
    #5
  7. 2012/02/19
    dnmacleod

    dnmacleod Well-Known Member

    Joined:
    2009/05/16
    Messages:
    419
    Likes Received:
    58
    It should be. Although I'm not conversant with pervasive.SQL, if I was doing that task in SQL Server, the installer would let me know of any incompatibilities during installation of the dbms.

    You are also doing quite a jump in versions but I would still expect queries to function correctly. An analogy might be a document that was prepared in Office 97 is perfectly readable in Office 2010 but the other way round? No chance.
     
    dnmacleod,
    #6
    mfctome likes this.
  8. 2012/02/19
    mfctome

    mfctome Inactive Thread Starter

    Joined:
    2011/01/20
    Messages:
    7
    Likes Received:
    0
    Thank you very much Don, I appreciate your time in responding to my query. The analogy is good too, I so love Microsoft and its 'backward compatibility'. It's always good that the new contains the old. Again, thank you. Michael Cooley
     
    mfctome,
    #7
  9. 2012/03/02
    dnmacleod

    dnmacleod Well-Known Member

    Joined:
    2009/05/16
    Messages:
    419
    Likes Received:
    58
    Yes, but its not just Microsoft that have to be backwards compatible. After all, its not much of a selling point for upgrading your existing customers if you're saying to them - "Here's the latest and greatest version of our flagship program, but, by the way, apart from it costing you $10,000 for the upgrade, you'll have to re-write all your existing files to be able to use it" :D

    How many customers do you think would upgrade?

    On the other hand, the point has to come where software companies have to bite the bullet and say "Look, we are not going to support upgrades from xx version any more." Thats what leaves many large companies running legacy software that no-one else uses any more - because they didn't upgrade their software when they had the opportunity. Now the cost of upgrading is so prohibitive, that they don't bother - they just carry on with their MS-DOS application that their own IT guys have had to bolt makeshift upgrades onto to make it work as they went along... :D
     
    dnmacleod,
    #8

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...