Database Reference
In-Depth Information
Imports and exports: The legacy database system might receive data
imports and can become the source of data exports. These imports and
exports might use DTS, converted to SSIS, or use other tools. You have
to isolate these requirements and make sure of the resulting upgraded
instance's correct participation.
Components referring to older SQL Server versions: If the user is selectively
transitioning legacy SQL Server instances, make sure that the resulting
instance of SQL Server 2008 has components that can still connect
successfully to the older SQL Server versions.
Drivers required for changing to a 64-bit version of SQL Server: These
required drivers might include drivers for accessing other database systems
and mainframes from a 64-bit server.
Patches, hotfixes, and cumulative updates: After you upgrade to SQL
Server 2008 from another edition of SQL Server, you must reapply any hotfix
or service pack updates to the upgraded SQL Server instance. The process
of Slipstream helps here to avoid spending time installing hotfixes or service
pack patch upgrades.
4.
Determine whether the upgrade was successful by using the following methods:
Upgrade to support SQL Server 2008.
Change connectivity settings.
Change authentication mode.
Accept the upgrade, and how it will make the "go/no-go" decision:
5.
Verify tests to ensure applications using the upgraded database servers run as
expected and required.
6.
If available, enlist the support of the QA team to develop appropriate
acceptance tests.
7.
Determine exactly when and how a rollback to the legacy SQL Server might
be required.
8.
Test the rollback plan.
If the application connectivity tests are successful, then the next step is to test the reporting
section. For instance, if the installation includes custom report items, assemblies, or
extensions, you must re-deploy the custom components. If you deployed and used any custom
extensions, or custom assemblies for reports with SSRS 2000 or SSRS 2005, you need to
redeploy the extensions or assemblies for use with SSRS 2008 R2.
These two steps need not necessarily be sequential. For example, you might apply some
acceptance criteria immediately to obtain a go/no-go decision. This could then be followed by
integrating the new instance and applying the remaining set of acceptance tests.
 
Search WWH ::




Custom Search