Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

Why Can't We Go Backwards? Expand / Collapse
Author
Message
Posted Tuesday, January 12, 2010 9:57 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 10:12 AM
Points: 31,209, Visits: 15,651
Comments posted to this topic are about the item Why Can't We Go Backwards?






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #846681
Posted Wednesday, January 13, 2010 2:34 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 9:18 PM
Points: 317, Visits: 408
While it would be a nice feature, I don't think it serves us well, especially with differences in datatypes between versions.

Sure you could try to force compatibility levels, but what happens if you have, say, a 2008 DB that you want to restore to 2005, and it has datetime2?
Post #846761
Posted Wednesday, January 13, 2010 4:49 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, January 18, 2011 4:19 AM
Points: 5, Visits: 12
Interesting.
I currently have a situation which is perhaps similar. I want to go forwards compatible.

We have a server on SQL 2005 and we want to upgrade it to SQL 2008. It would be really nice if we could just detach the databases, uninstall SQL 2005, install SQL 2008 and then reattach the databases.
But the question: is it that simple or will I encounter the issues you describe for backwards compatability when I go forwards?
Post #846796
Posted Wednesday, January 13, 2010 6:19 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Sunday, October 19, 2014 4:48 AM
Points: 1,327, Visits: 156
rwilkes; Depending on the versions, it can be that simple. When the databases from the previous version are attached, SQL Server will upgrade the databases to the current version. Actually, it can be more simple. You can upgrade in place, and the installation will upgrade the databases during its process. But check the installation compatibilities. For instance, you cannot upgrade SQL Server 7 databases directly to SQL Server 2008.




Mark
Post #846827
Posted Wednesday, January 13, 2010 6:39 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, January 18, 2011 4:19 AM
Points: 5, Visits: 12

Wow, thanks Mark. That almost sounds too good to be true!
We are going from SQL Server 2005 to 2008 so that probably helps make things fairly straight forward.

My only concern though is that you have suggested we could just upgrade with the dbs in place. I had heard it wasn't advisable to just upgrade, but that it was best to uninstall SQL Server 2005 before installing SQL Server 2008. Do you have a view on this?
(Obviously I'm all for the simple upgrade provided it doesn't have complicated connatations!)
Post #846837
Posted Wednesday, January 13, 2010 6:45 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 9:18 PM
Points: 317, Visits: 408
You can do an upgrade. I don't see the sense in uninstalling 2005 first.
Post #846839
Posted Wednesday, January 13, 2010 6:54 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Sunday, October 19, 2014 4:48 AM
Points: 1,327, Visits: 156
I have done both, with no noticeable problem either way. If it were a dedicated DB server, and running an older server OS, I would consider wiping it and installing latest OS (Windows Server 2008 R2) and a fresh clean install of SQL Server 2008. If the server has other functions/programs on it, an in-place upgrade may get you the benefits of SQL2008 quickly without reconfiguring other applications.



Mark
Post #846847
Posted Wednesday, January 13, 2010 6:55 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 10:12 AM
Points: 31,209, Visits: 15,651
Going backwards is an issue if you have changed the database. However in many cases, it isn't that you've changed the database, it's that you moved it to the next version and without changing it, and having it in a lower compatibility mode, you want to go back.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #846849
Posted Wednesday, January 13, 2010 6:58 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 9:18 PM
Points: 317, Visits: 408
Steve, agreed, which is why I think it would be a useful feature, but difficult to implement for the alternative (i.e. using the new features). For that amount of effort, scripting the DB out is "good enough". Yes?

EDIT: Clarified my statement.
Post #846853
Posted Wednesday, January 13, 2010 7:17 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 9:29 AM
Points: 2,610, Visits: 3,968
I will have to disagree on this one. What are the reasons to go back? The big one is that problems pop up in the new version and you need to go back. But, isn't that what testing is about? Test the database on the new version of SQL and find those issues before migrating the production database.

Are there are other reasons to go back to a prior version?

What kind of support nightmare do you have when upgrading some customers then moving them back?
Post #846870
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse