Test in Sql Server 2008, deploy to Sql Server 2005 sp4

Michael_Turek
Michael_Turek
in AppWorks #1

Planning on migrating but are still on v7.6...

 

We have a production server that although on SS 2005 sp4 - has high availability.

 

We have some test/staging servers with SS 2008 R2.

 

Although the ideal situation would to have all environments match database servers - some things are not possible budget wise...

 

Most times I will deploy from staging to prod, but there are cases that I would do the opposite to verify that I have the last updated prod map.  Is this a huge problem in terms of deploying across databases?  Will one map work differently from another just because the SS versions are different?

 

 

Tagged:

Comments

  • Jerome_Pearce
    Jerome_Pearce
    #2

    We have noticed any differences in behaviour when fdeployed to SQL Server 2005 or 2008. If you emply certain Transact SQL features they may possibly work in 2005 but not in 2008, but Metatsorm itself will not be affected.

  • Jefferson Garcia
    Jefferson Garcia
    #3

    On our previous migration to SQL 2008 from SQL 2005. We have made some adjustments on the indices so you may want to check this especially if you are running performance tests on SQL 2008 box then you will restore to SQL 2005.

  • McGaw_Phil
    McGaw_Phil
    #4

    Hi,

     

    To make your life easier throughout all your environments, couldn't you just set the compatibility mode to SQL Server 2005 for the metastorm database in all your environments.  This way it doesn't matter if you are hosted on a SQL Server 2008 instance or 2005 instance.

     

    Naturally if you are using SQL 2008 features then this isn't possible, but I'm guessing testing would be failing in your non-production environments if this was the case.

     

    SqlServer_CompatibilityLevel.JPG

     

Categories

image
OpenText CE Products
AppWorks
Gateway & Platform