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 12»»

Upgrade Strategies for SQL Server 2008 Expand / Collapse
Author
Message
Posted Saturday, February 28, 2009 7:37 PM


Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, July 3, 2014 6:25 AM
Points: 64, Visits: 189
Comments posted to this topic are about the item Upgrade Strategies for SQL Server 2008

With Thanks and Regards
Arshad Ali
Microsoft India

My Blog - http://arshadali.blogspot.com/
Post #666218
Posted Monday, March 2, 2009 12:21 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, September 1, 2014 6:55 AM
Points: 2,365, Visits: 1,845
Nice article.

After a doing side by side upgrade the databases are moved to the new instance by dettach/attach or backup/restore. Will this change the compatibility level of the database being moved to sql 2008 instance.


"Keep Trying"
Post #666383
Posted Monday, March 2, 2009 2:39 AM


Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, July 3, 2014 6:25 AM
Points: 64, Visits: 189
In my experiment from Microsoft SQL Server 2005 - 9.00.3042.00 to Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 upgrade of user database using backup/restore and attach/detach, it didn't change the compatibility level.

Here are few lines from MSDN:
Database Compatibility Level After Upgrade
The compatibility levels of the tempdb, model, msdb and Resource databases are set to 100 after upgrade. The master system database retains the compatibility level it had before upgrade, unless that level was less than 80. If the compatibility level of master was less than 80 before upgrade, it is set to 80 after upgrade.

If the compatibility level of a user database was 80 or 90 before upgrade, it remains the same after upgrade. If the compatibility level was 70 or less before upgrade, in the upgraded database, the compatibility level is set to 80, which is the lowest supported compatibility level in SQL Server 2008.


More details can be found here:
http://msdn.microsoft.com/en-us/library/bb933942.aspx


With Thanks and Regards
Arshad Ali
Microsoft India

My Blog - http://arshadali.blogspot.com/
Post #666428
Posted Monday, March 2, 2009 4:10 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, September 1, 2014 6:55 AM
Points: 2,365, Visits: 1,845
Thanks.

In a perfect world should'nt the compatibility level also change?


"Keep Trying"
Post #666459
Posted Friday, March 27, 2009 7:26 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, November 21, 2013 6:45 AM
Points: 1, Visits: 76
Has anyone else problems with DB copy wizard? Source is MSSQL 2000, method is SQL Management objects. I need to keep the source DBs online, so detach-attach is out of question.
Microsoft (R) SQL Server Execute Package Utility Version 10.0.1600.22 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 13:44:08
Progress: 2009-03-27 13:44:09.16
Source: mssql03_PKSQL2008_Transfer Objects Task
Task just started the execution.: 0% complete
End Progress Error: 2009-03-27 13:44:35.81
Code: 0x00000000
Source: mssql03_PKSQL2008_Transfer Objects Task
Description: ERROR : errorCode=-1073548784 description=Executing the query "CREATE VIEW [dbo].[PoctyOS] AS SELECT dbo.Se..." failed with the following error: "Invalid object name 'dbo.Servers'.".

This happens for any database I've tried - always it reports some "invalid object name" or "invalid column name" and of course the "invalid" object is there.
Post #685029
Posted Wednesday, April 29, 2009 4:29 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, February 22, 2014 6:12 PM
Points: 3, Visits: 22
We are doing a test run on updating SQL 2005 Standard Edition to SQL 2008 Standard Edition.



We are doing this on a fresh install of the server and SQL 2005 and in the process, we renamed the computer after 2005 was installed.

We did run the sp_dropserver and sp_addserver sprocs with the old name and new names and restarted our default instance.

We have made it to the step entitled Reporting Services Authentication.

We only have a default instance of 2005 installed. The text box labeled "Instance of SQL Server that hosts the report server database" is not editable and looks like it should contain the machine name, however it contains the old server name. Is there a chance that this value is coming from the RSReportServer.config file. Does anyone know of a way to check the contents of this file and of the best way to change the contents to reflect the new machine name?

Thanks.
Post #707283
Posted Wednesday, June 3, 2009 11:55 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, December 14, 2013 2:35 PM
Points: 6, Visits: 42
I have a question about the upgrade from 2005 to 2008... should you script all of your logins from master and script all the jobs and SSIS packages from MSDB and apply to the new 2008 (side by side update) or can you detach and attach your current Master and MSDB from 2005 to 2008?

Thanks...
Post #728683
Posted Saturday, March 6, 2010 5:31 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Sunday, February 2, 2014 1:01 PM
Points: 849, Visits: 130
I faced a similar issue but it was because the dba's had turned off dbo schema access in 2008 for developers.
Post #878142
Posted Saturday, March 6, 2010 5:42 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Sunday, February 2, 2014 1:01 PM
Points: 849, Visits: 130
gaurav.bhagat (3/6/2010)
I faced a similar issue but it was because the dba's had turned off dbo schema access in 2008 for developers.


Seems sqlservercentral forums need database tuning. I was trying to edit my above post to link it to 2000-2008 conversion post but I kept getting the default error page from the forums application -- looks like timeouts. Hopefully this one posts!!!
Post #878143
Posted Saturday, March 6, 2010 9:54 AM


Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, July 3, 2014 6:25 AM
Points: 64, Visits: 189
You need to script out jobs/logins and run the script on the SQL Server 2008. I think simply detach and attach of these system databases (master/msdb) will not work becuase of some internal table/sp name changes between versions.

With Thanks and Regards
Arshad Ali
Microsoft India

My Blog - http://arshadali.blogspot.com/
Post #878182
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse