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

SQL Server 2008 Upgrade Gotchas & Fixes Expand / Collapse
Author
Message
Posted Thursday, March 25, 2010 12:13 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, August 24, 2011 10:56 PM
Points: 215, Visits: 679
1
) Reporting Services (RS) is required for the Upgrade Advisor
This is a logical gotcha that kinda makes me mad. Microsoft Best Practices and our corporate security guidelines state that you should not put Reporting Services on the same server as an Operational Data Store (ODS). The crux of the matter is that the SQL Upgrade Advisor (SUA) has to be on the server that it is scanning. It makes much more sense that the SUA be installed on a separate RS server and pointed towards the target server with a connection object. I went ahead and installed RS on the first dev server and then ran the SUA scan.

The scan revealed nothing I didn't already know. Secondly, the SQL upgrade program does a similar scan, which will reveal any show stoppers. I made a judgment call and decided not to run SUA on servers that don't already have RS on them.


Do we need to install SQL Server 2005 Reporting Services OR SQL Server 2008 Reporting Services on where we run SQL Server 2008 upgrade adviser?

thanks
Post #890137
Posted Thursday, March 25, 2010 4:18 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, April 11, 2014 1:02 PM
Points: 64, Visits: 360
The SQL Server 2008 Upgrade advisor is designed to work with SQL Server 2005 Reporting Services.

For more information look here:

http://msdn.microsoft.com/en-us/library/bb677622.aspx

Cheers!

Brandon_Forest@sbcglobal.net
Post #890293
Posted Wednesday, April 07, 2010 9:56 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, August 13, 2010 1:02 PM
Points: 12, Visits: 25
There is some good information here but corrections/clarifications that need to be made -

Item #1) Reporting Services is NOT a requirement to run the SQL Server Upgrade Advisor!
a. The location where you install SQL Server Upgrade Advisor depends on what you will be analyzing. Upgrade Advisor supports remote analysis of all supported components except Reporting Services. If you are scanning instances of Reporting Services, you must install Upgrade Advisor on the report server.
b. If you are not scanning instances of Reporting Services, you can install Upgrade Advisor on any computer that can connect to your instance of SQL Server, and that meets the Upgrade Advisor prerequisites.
Additional information - http://msdn.microsoft.com/en-us/library/ms144256.aspx


Item #3) Visual Studio 2008 - SP1 required for any v3.5 .NET components - NOT TRUE!
Visual Studio Sp1 is only required if you have Visual Studio installed and you plan on using Visual Studio after you upgrade to SQL Server 2008. If you don't plan on using it, then, technically, you don't have to upgrade it. If you have not installed Visual Studio 2008 RTM but are getting the error that VS SP1 is required, it is because Visual Studio 2008 Shell (integrated mode) is installed on your system but not at the SP1 level. This is probably because it was left over from a SQL Server 2008 CTP installation.

The binaries needed from VS 2008 SP1 are not related to the .Net Framework 3.5 SP1 update. SQL Server 2008 does require the .Net Framework 3.5 SP1 update but for different reasons. SQL Server 2008 setup will install the released version of .Net Framework 3.5 SP1 if it detects it is not already installed. This is one of the first things SQL Server 2008 setup does when executed. Even if you have the .Net Framework 3.5 SP1 Beta, SQL Server 2008 will update it to the RTM version of .Net Framework 3.5 SP1.
See this article for more information - http://blogs.msdn.com/joaol/archive/2008/08/29/sql-server-2008-visual-studio-2008-sp1-and-net-framework-3-5-sp1-explained.aspx


Finally, to answer the post by SSCrazy - yes, the SQL Server 2008 workstation tools are backwards compatible with SQL Server 2000 & 2005... of course, with limited functionality depending on the versions and features supported on the version you're connecting to.
http://msdn.microsoft.com/en-us/library/ms174190.asp



Post #899247
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse