Sql server 2012 Upgrade Technical Guide Writers
SQL Server 2012 Upgrade Technical Guide
Yüklə 8,9 Mb. Pdf görüntüsü
|
- Bu səhifədəki naviqasiya:
- SQL Server 2012 Upgrade Technical Guide
- Upgrading via the Setup Application
- Side-by-Side Upgrade
- Installing the New Instance
- Configuring the New Instance
- Troubleshooting a Failed Upgrade
- Post-Upgrade Tasks
- Standard and custom data extensions.
410
Server 2008 SP2 relational engine, with the new database schema in place. If a SQL Server 2005 Database Engine instance is hosting the report server database, you cannot upgrade the Reporting Services component without upgrading the relational engine. If the report server database resides within a named instance of SQL Server on the same server or resides on a remote server (SQL Server 2005), you must upgrade the Database Engine instance hosting the report server database first and then upgrade the
Reporting Services component. Upgrading via the Setup Application Upgrading from SSRS 2008 R2 to SSRS 2012 via the Setup application is identical to upgrading from SSRS 2005 via the Setup application. For detailed steps, see “Upgrading via the Setup Application” in the “Upgrading from SQL Server 2005” section earlier in this chapter.
Upgrading from SSRS 2008 R2 to SSRS 2012 via the side-by-side method is identical to doing a side-by-side upgrade from SSRS 2005. For detailed steps, see “Side-by-Side Upgrade” in the “Upgrading from SQL Server 2005” section earlier in this chapter. Installing the New Instance The steps and options for installing the new instance are the same as in an SSRS 2005 upgrade. You can find those steps in the “Installing the New Instance” section under “Upgrading from SQL Server 2005.” Configuring the New Instance After you have installed the new SSRS 2012 instance, you should use the Reporting Services Configuration tool to configure it. Start the tool from the Configuration Tools group within the Microsoft SQL Server 2012 Start menu group. The steps for configuring the new instance are the same as in an SSRS 2005 upgrade. You can find those steps in “Configuring the New Instance” in the “Upgrading from SQL Server 2005” section earlier in this chapter.
If the upgrade process should fail, the first course of action is to review the setup logs created by the Setup application.
411
Review the Summary.txt file located in the Server\110\Setup Bootstrap\LOG\ directory. If any error messages are listed, take the required actions to correct the situation and try the upgrade process again. Each execution of Setup will generate a new time-stamped log folder. For example, if you start the SQL Server Installation Center page, it gets its own time-stamped log folder, and each Setup action invoked from that page gets its own as well, so you will probably see several time-stamped log folders in this directory. The time-stamped log folder name format is YYYMMDD_hhmmss. You can find detailed Setup logs at the following location: Files\Microsoft SQL Server\110\Setup Bootstrap\LOG\. When looking for errors in the detail log, search for the following phrases:
Watson bucket
Error:
Exception has been A typical Setup request goes through three execution phases: 1.
2.
Component update 3.
User-requested action Each of these phases will generate detail and summary logs, with additional log files being generated as appropriate. Setup is called at least three times per user-requested Setup action. Typical log files generated are:
Detail_ComponentUpdate.txt
Detail.txt The summary log filename format is Summary_[machine name]_timestamp_[execution phase]. The final summary log is copied to %Program Files%\Microsoft SQL Server\110\setup bootstrap\log folder and named Summary.txt for quick reference.
412
Windows Installer (MSI) actions performed during Setup generate their own log files in the following format: [product feature]_[cpu]_[LCID (optional)]_[attempt #].log. If an MSI execution fails, look in the associated MSI log for “return value 3” only for ENU versions.
Datastore files contain a snapshot of the state of all configuration objects being tracked by the Setup process and are useful for troubleshooting configuration errors. XML file dumps are created for datastore objects for each execution phase. They are saved in their own log subfolder under the time-stamped log folder, as follows:
Datastore_GlobalRules
Datastore_ComponentUpdate
Datastore For more information, see View and Read SQL Server Setup Log Files
(http://msdn.microsoft.com/en-us/library/ms143702(v=sql.110).aspx) in SQL Server 2012 Books Online. Post-Upgrade Tasks After upgrading to SSRS 2012 from SSRS 2005, SSRS 2008, or SSRS 2008 R2, it is important to ensure that the upgrade ran successfully and to configure SSRS 2012: 1.
To begin, particularly if you performed an in-place upgrade, use the Reporting Services Configuration tool to check the configuration of the report server. After the tool is launched, connect to the upgraded instance. 2.
Review the configuration settings by selecting each of the items in the left pane of the tool. If any of the settings seem incorrect or are missing, update the settings and save the changes. 3.
Ensure that the report server is behaving as expected by running a sample set of the reports deployed to the server. Start Report Manager by using the correct URL (for example, http://locahost/Reports for an upgraded default instance or http://localhost/Reportsnew for a newly installed and configured named instance). At a minimum, you should select and execute reports to verify that the following report server features and capabilities (if used) are working correctly:
against all defined data sources (using standard data providers or custom data extensions) to ensure that each is working as expected. Yüklə 8,9 Mb. Dostları ilə paylaş:
|