SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server 2008 Upgrade Gotchas & Fixes


SQL Server 2008 Upgrade Gotchas & Fixes

Author
Message
pshaship
pshaship
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1161 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
Brandon Forest
Brandon Forest
SSC-Addicted
SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)SSC-Addicted (411 reputation)

Group: General Forum Members
Points: 411 Visits: 446
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
danarivk
danarivk
SSC Journeyman
SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)

Group: General Forum Members
Points: 78 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



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search