IBM i2 ibase 8 Upgrading IBM i2 ibase databases to SQL Server 2005 or 2008 VERSION MAY 2012

Transcription

1 IBM i2 ibase 8 Upgrading IBM i2 ibase databases to SQL Server 2005 or 2008 VERSION MAY 2012

2 Note: Before using this information and the product it supports, read the information in Notices on page 20. This edition applies to version 8, release 9, modification 1 of IBM i2 ibase (product number G15) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces part number Copyright International Business Machines Corporation 1991, US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contacting IBM Support IBM Support provides assistance with product defects, answers FAQs, and helps users resolve problems with the product. Before you begin After trying to find your answer or solution by using other self-help options such as technotes, you can contact IBM Support. Before contacting IBM Support, your company or organization must have an active IBM software subscription and support contract, and you must be authorized to submit problems to IBM. For information about the types of available support, see the Support portfolio topic in the Software Support Handbook. Procedure To contact IBM Support about a problem: 1. Define the problem, gather background information, and determine the severity of the problem. For more information, see the Getting IBM Support topic in the Software Support Handbook. 2. Gather diagnostic information. 3. Submit the problem to IBM Support in one of the following ways: Online through the IBM Support Portal at You can open, update, and view all of your service requests from the Service Request portlet on the Service Request page. By phone: For the phone number to call in your region, see the Directory of worldwide contacts web page at Results If the problem that you submit is for a software defect or for missing or inaccurate documentation, IBM Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM Support website daily, so that other users who experience the same problem can benefit from the same resolution. Publication number SC

3 Contents IBM i2 ibase Upgrading IBM i2 ibase databases to SQL Server 2005 or Contacting IBM Support...2 Contents...3 Who should read this white paper?...3 Reasons for upgrading...3 Best practices...5 Performing a direct upgrade of SQL Server...7 Migrating SQL Server...10 Troubleshooting...17 Appendix A: Prerequisites for Analyst s Workstation...19 Appendix B: Additional information...19 Notices...19 Trademarks...21 Who should read this white paper? This document provides guidance for people involved in upgrading IBM i2 ibase and IBM i2 Analyst's Workstation databases from SQL Server 2000 to SQL Server 2005 or It assumes that a trained SQL Server DBA is available to assist the reader as they follow the guidance. This document is designed to provide sufficient information to help you to plan and execute your upgrade to SQL Server 2005 or Note: This supersedes ibase 8: Upgrading ibase databases to SQL Server 2005 or later (Issue 3, Part number 2537). Reasons for upgrading ibase 8.9 does not support SQL Server 2000, so you must upgrade from SQL Server 2000 to SQL Server 2005 or 2008, before you begin the upgrade to ibase 8. There are two main upgrade paths that you can follow: A direct upgrade, in which you upgrade the software in place, on the existing hardware A migration upgrade, in which you install and set up the software on separate hardware before bringing the data across from the original system Upgrading directly and migrating both use the same SQL Server installers. To upgrade an existing instance of SQL Server, you must select it during installation. Note: Migrating or upgrading directly from SQL Server 2000 to SQL Server 2005 or 2008 is more involved than migrating or upgrading directly from SQL Server 2005 to SQL Server 2008, particularly if you use Analyst s Workstation. No special steps are necessary for ibase 8 to work after migrating or upgrading directly from SQL Server 2005 to SQL Server

4 Advantages of directly upgrading SQL Server Provided the hardware meets the minimum requirements of SQL Server 2005 or 2008, no additional hardware is required to upgrade. No change needs to be made to the ibase security and database connection files. Disadvantages of directly upgrading SQL Server If your SQL Server machine hosts databases for applications other than ibase, all those applications will also have to be compatible with SQL Server 2005 or Versions of ibase that precede ibase do not support SQL Server 2005 or Therefore, if you are retaining some of your databases for use with one of these versions of ibase, they must be on a server that is not going to be upgraded to SQL Server 2005 or The SQL Server will be offline for some time during the upgrade. Advantages of migrating databases You have finer control over which databases will be converted to SQL Server 2005 or You do not need to perform the migration of all databases on an SQL Server instance at the same time. It is possible to spread the workload. Hence only the users of a single database or security file are affected by the migration. If you leave a copy of your database on the source server, you can use this original database for testing and verification. If a migration fails, you can easily bring the source database back online and try to resolve the issues in the migration while the users continue to work on the source database. You can consolidate all your ibase databases onto one instance of SQL Server. Disadvantages of migrating databases If you intend to use the same hardware for your destination SQL Server instance, you will have to give the new instance a new name. Even if you intend to delete the original instance after migration is complete, you will not be able to rename the new instance to the name of the deleted instance. You will have to reconfigure your security and database connection files to reference the new SQL Server instance. You may require extra hardware to run the source and destination instances alongside each other. 4

5 Best practices Ensure you are using a version of ibase that is compatible with the SQL Server version If you are currently running on an earlier version of ibase than ibase 5.0.9, it is recommended that you should upgrade the database to ibase before attempting to upgrade to SQL Server 2005 or As this is a database change, this upgrade will only need to be applied to a single machine with access to the database. Once the upgrade to ibase has been successfully completed, open the database using ibase Designer before starting the SQL Server upgrade. If you have already upgraded to ibase 8.0 or 8.1, you should remove your Full-text Search Indexes before upgrading your SQL Server version. You should also suspend alerting via the Alerting Configuration dialog. If you have already upgraded to ibase 8.0, 8.1, or 8.5, upgrade to 8.9 before upgrading SQL Server. Test the upgrade first Always perform changes to SQL Server in a test environment before performing it on a live system. Note: The test environment you use should closely match your current system, allowing you to troubleshoot any issues that arise. Communicate with all system users Once the upgrade testing has been successfully completed, you should send a communication to all system users advising them of the planned work, timescales, and how this will affect them. Note: You should continue this communication throughout the process, alerting users to the progress that has been made. Back up your system It is of utmost importance that you make a complete backup of your existing ibase configuration and databases, and verify they are successfully backed up before and after you perform the upgrade. Ensure the correct SQL Server password strength The SQL Server database administrator (DBA) password policy was strengthened in SQL Server 2005 and this change enforced in SQL Server To prevent access problems, ensure your password is strong before beginning the upgrade process. Follow the recommended Microsoft SQL Server upgrade path This document assumes that you are familiar with SQL Server administration, and that you will refer to the recommended Microsoft SQL Server literature when planning your upgrade. This should include all prerequisite checks and post upgrade steps. For more information please refer to the following Microsoft resources: SQL Server 2005 Upgrade Handbook Upgrading to SQL Server

6 Full Text Indexing If your database has a Full Text index, the index should be removed before starting the upgrade process. To remove the Full Text Index: 1. Open the database in IBM i2 ibase Designer. 2. Select Tools > Search > Full-Text Search Indexing. 3. Deselect All Entity and Link Type nodes. 4. Press OK. A message box will appear: 5. Select Yes to delete your index. Once the upgrade is complete, your Full Text Search should be rebuilt if required. For information on rebuilding your Full Text Search index please refer to the ibase Designer Online Help. Alerting While the upgrade is in progress, you should disable any ibase alerting jobs. Additional actions for users of ibase 8 Scheduler When making any changes to the database, you should ensure that the ibase Scheduler has completed any outstanding import or export tasks and has been turned off before the change takes place. If Scheduler databases are on more than one SQL Server, an alternative to stopping the Scheduler service is to deactivate any Scheduler triggers that operate over the databases on the server you are upgrading. This will ensure that scheduled imports for databases on other servers continue unaffected. Once the upgrade has completed, enable ibase 8 Scheduler to perform its imports and exports by either starting the Scheduler service or reactivating the Scheduler triggers using the ibase 8 Scheduler Configuration tool. Additional actions for replicated databases When making any changes to the database, you should ensure that the SQL Server DBA has removed database replication before the changes are carried out. Replication of the audit log is optional, but if you have chosen to replicate it, the SQL Server DBA must remove replication on this database too. Once the change is complete, the SQL Server DBA should reconfigure replication between the servers before allowing any users to access the database again. 6

7 Performing a direct upgrade of SQL Server You can upgrade SQL Server 2000 to SQL Server 2005 or 2008 in one step by running the relevant SQL Server installer and selecting an existing instance of SQL Server All your existing ibase databases that reside on the SQL Server instance will be upgraded from SQL Server 2000 to SQL Server 2005 or In summary, the upgrade process is: 1. Identify all instances of SQL Server 2000 that ibase uses. 2. Identify any databases that cannot be upgraded and the reasons why. (Warning: Do not proceed if any such databases are found.) 3. Back up all databases on the SQL Server instances. 4. Install Microsoft SQL Server 2005 or 2008, choosing the option to upgrade an existing instance. 5. Complete the upgrade. 6. Repeat steps 2 through 5 for all identified instances of SQL Server. Note: When performing a direct upgrade of a SQL Server database, all security and audit databases must be upgraded at the same time. Identifying all instances of SQL Server 2000 that ibase uses As part of the upgrade, you will need to gather the names of all the ibase databases and the SQL Servers that host them, and whether they are security, data, or audit databases. For further information on identifying these file names, please refer to the white paper named Upgrading to IBM i2 ibase 8 or IBM i2 Analyst's Workstation 8. Whether a particular instance is upgraded will depend on any issues discovered during the following phase. Identifying databases that cannot be upgraded Any databases on an instance of SQL Server that are neither an ibase database nor a SQL Server system database can block the upgrade, if the application that uses the database has not been certified on the newer version of SQL Server. If you find databases that are not ibase databases, you will need to verify whether the database can be upgraded to the newer version of SQL Server before proceeding with the upgrade of the SQL Server. When a server hosts databases for other applications, you have a number of options, some of which are summarized in the following list: Move the databases for the other application onto another instance of SQL Server. You will have to update the client application to point to the new instance of SQL Server. Migrate the ibase databases to a new SQL Server instance. This may be an easier option than moving a database that cannot be upgraded. However, if you find that all your SQL Server instances host both ibase and non-ibase databases, you will either have to set up a newer SQL Server instance solely for the ibase databases, or shuffle ibase and non-ibase databases between your servers. Establish whether your non-ibase databases can be upgraded to the SQL Server version, and continue with the upgrade. Leave all databases where they are and do not upgrade the server. 7

8 Backing up all databases on the SQL Server Before upgrading, you must ensure that a full backup has been made of all database files. Additional actions for users of ibase 8 Scheduler Before backing up the databases, ensure that the Scheduler service on the machine that is used to run scheduled tasks is not in the process of performing an import or export in any database on this server. Also, ensure that the service is in the stopped state. If Scheduler databases are on more than one SQL Server, an alternative to stopping the Scheduler service is to deactivate any Scheduler triggers that operate over the databases on the server you are upgrading. This will ensure that scheduled imports for databases on other servers continue unaffected. Prior to performing the backup: 1. Ensure there are no users accessing the database. 2. Set the user access option on the SQL Server database to single-user. Provided that the DBA does not exit the database, only the SQL Server DBA will have access to the database, preventing changes from being made during the backup. The SQL Server DBA can backup the database, and then take it offline for the duration of the upgrade. This will ensure that no user accesses the database after the backup is made. Additional actions for Analysis Services databases Backup the Analysis Services databases for the ibase databases on the SQL Server instance that is to be upgraded. After all the Analysis Services databases have been backed up for a database, ask the SQL Server DBA to allow users into the database to delete all their existing Data Miner cubes. Deleting the cubes through Data Miner will delete the entry in the cube register within the ibase database, and also delete the Analysis Server cubes. The Analysis Services databases will remain on the Analysis Server but the SQL Server DBA should delete them manually. Once this has been completed, ask the SQL Server DBA to again backup the database then take it offline. Installing Microsoft SQL Server 2005 or 2008 Perform the upgrade of the SQL Server instance. The SQL Server instance will be unavailable during most of this process. The original SQL Server binaries will be replaced, and the databases will be upgraded. After the upgrade, it will not be possible to back up the databases with the intention of restoring them onto an earlier SQL Server instance. Additional actions for Analysis Services databases The Analysis Services server may still host Data Miner cubes from ibase databases that reside on an earlier instance of SQL Server. If you upgrade the Analysis Services installation, the Data Miner users of the earlier instance of SQL Server will not be able to access the cubes, which will then reside on the later instance of the Analysis Services server. Consider installing a new instance of Analysis Services for use with the ibase databases that use the later SQL Server version. 8

9 Completing the upgrade On completion of the upgrade, bring the databases back online, and open the database using ibase Designer. (Ensure that this is done using an SQL login that has dbo rights in the main database and the audit log database.) The Full Text Search may be rebuilt if required. For information on rebuilding your Full Text Search index please refer to the ibase Designer Online Help. Once the changes made by ibase Designer have been completed, set the user access option on the SQL Server database to multi-user, and confirm that the users are able to access the databases successfully. Perform a full backup of all databases on the server after completing the upgrade to SQL Server 2005 or Additional actions for a replicated database If you have implemented ibase 8 Database Replication, and you elected to leave your publications and subscriptions active during the upgrade, your data will not continue to replicate until you have performed the following operations: On the publishing server: Update all publication database snapshots Restart the merge agents for all push subscriptions On the subscriber servers: Restart the merge agents for all pull subscriptions Until the snapshots are updated and the subscribers have synchronized, the following error message will be displayed when attempting to update the contents of a replicated database: Table table_name into which you are trying to insert, update, or delete data is currently being upgraded or initialized for merge replication. On the publisher, data modifications are disallowed until the upgrade completes and snapshot has successfully run. On the subscriber, data modifications are disallowed until the upgrade completes or the initial snapshot has been successfully applied and it has synchronized with the publisher. Additional actions for users of ibase 8 Scheduler Restart the Scheduler service (or reactivate the Scheduler triggers, if you chose to deactivate them), and then test that your scheduled imports and exports are working correctly. 9

10 Additional actions for Analyst's Workstation client machines Through Data Miner, an Analyst's Workstation client machine can be configured to access a Microsoft SQL Server 2005 Analysis Server, a Microsoft SQL Server 2008 Analysis Server, or any combination of these. To configure your client machine to access a SQL Server 2005/2008 Analysis Server, you must: Ensure that all prerequisites are installed (See Appendix A: Prerequisites for Analyst's Workstation). Note: Please refer to the System Requirements section of the IBM i2 Analyst s Workstation Release Notes for further information. Modify the Data Miner registry settings to enable Data Miner to build cubes on an instance of Microsoft SQL Server 2005/2008 Analysis Server. Note: Please refer to the topic Specifying which Analysis Server to Use for Cube Building in the Administration Center for further information. Additional actions for Analyst's Workstation databases You may wish to rebuild your main Data Miner cubes ready for your users when they access the database. All saved cube definitions will still be in the database, so the users can rebuild non-essential cubes as and when they require them. Migrating SQL Server Database migration requires that you set up a new instance of SQL Server 2005 or When the new instance is installed and configured, you can move your databases from the source instance of SQL Server 2000 to the destination instance of SQL Server 2005 or There are various methods for migrating SQL Server databases between servers, including: Backup and restore Detach and attach The copy database wizard For illustration, this paper uses the backup/restore method. A benefit of this method is that the original database will still exist on the source server after the migration, allowing for side-by-side comparisons of the databases. Once you are satisfied with the migration, you can delete the source database. The ibase connection file will reference the source database until you reconfigure the connection file properties to reference the destination database. Note: Access to the SQL Server machine/instance and the databases it hosts will require the assistance of a SQL Server DBA. 10

11 The migration process differs depending on whether you are migrating a SQL Server ibase security file, or a SQL Server ibase database. To migrate a security file: 1. Obtain the security file properties 2. Obtain the database file properties 3. Back up the security file database 4. Restore the security file database 5. Reconfigure the security connection file To perform a database migration: 1. Obtain the database file properties 2. Back up the database and audit log 3. Create a new database on the new machine using ibase 4. Restore the existing database and audit log over the top of the newly created database 5. Reconfigure the database connection file Obtaining the security file properties As part of the upgrade, you will need to gather the names of all the ibase databases and the SQL Servers that host them, and whether they are security databases or data databases. For further information on identifying these file names, please refer to the white paper named Upgrading to IBM i2 ibase 8 or IBM i2 Analyst's Workstation 8. To obtain the security file properties: 1. Choose a security file to upgrade. 2. Log on to the security file through ibase Designer as a user with security administrator privileges. 3. From the File menu, select Security File Properties. 4. Confirm that the security file type is SQL Server, and make a note of the following information that is required to perform the backup: the security file s database name the SQL Server name and instance Note: A security file that has not been upsized from Microsoft Access to SQL Server does not need to go through the migration process. Obtaining the database file properties You need to obtain the database file properties during security file migrations and database migrations, because security file migration requires the database password. To obtain it: 1. Log on to ibase Designer as a user with system administrator privileges. 2. Open a database that is secured by the security file. 3. From the Tools menu, select Feature Availability > Options. 4. The database password is displayed at the bottom of the Advanced tab. Make a note of this password. (The password is not displayed to users that do not have system administrator privileges.) 11

12 To obtain the database file connection properties necessary for a database migration: 1. Log on to ibase Designer as a user with security administrator privileges. 2. Open a database that is secured by this security file. 3. From the File menu, select Database Properties. 4. Confirm that the database file type is SQL Server, and make a note of the following information that is required to perform the backup: the database name the SQL Server name and instance Note: A database that has not been upsized from Microsoft Access to SQL Server does not need to go through the migration process. Backing up the security file To perform the backup, the SQL Server DBA should: 1. Ensure no users are accessing the SQL Server database component of the security file. 2. Remove the replication of the security file, if it is being replicated. 3. Set the user access option on the SQL Server database to single-user. Provided that the DBA does not exit the database, only the SQL Server DBA will have access to the database, preventing changes from being made during the backup. 4. Back up the security file database, and then take it offline. This ensures that users are unable to access the security file database after the backup is made. 5. Ask the network administrator to move the backup file to the SQL Server 2005 or 2008 machine in preparation for the restore operation. Restoring the security file Your SQL Server DBA can restore the security database from the backup onto the destination server. The name supplied for the database must be identical to that of the source database, because the database name specified in the connection file cannot be altered through the ibase 8 Database Configuration tool. Note: Users will not be able to access the destination database until after you reconfigure the connection file. After the security database has been successfully restored, your SQL Server DBA can set the user access option on the destination SQL Server database to multi-user, in preparation for the reconfiguration of the security connection file. Reconfiguring the security connection file To allow users to connect to the SQL Server 2005 or 2008 version of the security file, you must reconfigure the connection file to point to the destination server and database. This requires the following information: the path to the security connection file the database password the SQL Server and instance name 12

13 To reconfigure the security connection file: 1. Open the ibase 8 Database Configuration tool. From the Windows Start menu, select All Programs > IBM i2 ibase 8 > Tools > ibase Database Configuration: 2. Browse to the location of the security connection file you wish to reconfigure. 3. Do not enter a value for the database file name. Doing so instructs the tool to reconfigure the database connection file instead of the security connection file. 4. Enter a value for the user name. There is no need to enter the password for this user, because the security database on the source server is offline it will not be possible to validate the user credentials. Instead, the security connection file contains the database password, but its value is only accessible by ibase system administrators. This value will be used to determine whether you are an ibase system administrator. If the security file is still online, you will be informed that an incorrect value has been entered for the user name or password. 5. After you click Next, but before the connection properties are displayed, ibase requests the database password: 13

14 6. After validating the database password, you are able to reconfigure the security file connection settings: 7. Change the server name to that of the destination server. Notice that it is not possible to alter the SQL Server database name. 8. Ensure you turn on the Test connection before saving check box. Doing so will alert you to any configuration errors that are preventing a successful connection to the security database. 9. Save the configuration details and test that your ibase users are able to log on to the security file successfully, now that the connection file references the database on the destination server. Backing up the database and audit log The audit log records activity in the database. It is therefore necessary to keep the database and the audit log synchronized during the backup, so that the audit log will accurately reflect database activity if they need to be restored. To ensure this happens, back up the database and take it offline before starting the audit log backup. Additional actions for users of ibase 8 Scheduler Before backing up the databases, ensure that the Scheduler service on the machine that is used to run scheduled tasks is not in the process of performing an import or export in any database on this server. Also, ensure that the service is in the stopped state. If Scheduler databases are on more than one SQL Server, an alternative to stopping the Scheduler service is to deactivate any Scheduler triggers that operate over the databases on the server you are upgrading. This will ensure that scheduled imports for databases on other servers continue unaffected. 14

15 To perform the database backup, the SQL Server DBA should: 1. Ensure no users are accessing the SQL Server database. 2. Remove the replication of the database, if it is being replicated. 3. Set the user access option on the SQL Server database to single-user. Only the SQL Server DBA will have access to the database, preventing changes from being made during the backup. 4. Back up the SQL Server database, and then take it offline. This will ensure that users are unable to access the database after the backup is made. 5. Repeat steps 1 through 4 for the audit log database. 6. Ask the network administrator to move the backup files to the SQL Server 2005 or 2008 machine in preparation for the restore operation. Additional actions for Analysis Services databases Back up the Analysis Services databases for the ibase databases on the SQL Server instance that is to be upgraded. After all the Analysis Services databases have been backed up for a database, ask the SQL Server DBA to allow a single user into the database to delete all the existing Data Miner cubes. Deleting the cubes through Data Miner will delete the entry in the cube register within the ibase database, and also delete the Analysis Server cubes. The Analysis Services databases will remain on the Analysis Server but the SQL Server DBA should delete them manually. Once this has been completed, ask the SQL Server DBA to take the database offline. Restoring the database and audit log Logged on as a SQL Server DBA, restore the SQL Server database from the backup to the destination server. The name you supply for the database must be identical to that of the source database; it is not possible to alter the database name through the ibase 8 Database Configuration tool. Note: Users will not be able to access the destination database until after you reconfigure the connection file. After the database has been successfully restored, you can set the user access option on the destination SQL Server database to multi-user, in preparation for the reconfiguration of the database connection file. Ensuring that you are running in the correct SQL compatibility mode In order to ensure that all the new features of ibase 8 will work correctly, you should check that the compatibility mode for your database now matches the version of SQL Server you have installed: 1. Ensure that you are logged into the system as a system administrator. 2. Open SQL Server Management Studio. 3. Right-click the Database. 4. Select Properties > Options > Compatibility level. 5. Choose the correct option for your SQL version, for example SQL Server 2005 (90) for SQL Server 2005 databases. Note: These steps need to be performed on the main database, the audit log database and the security database (if applicable) immediately after restoring the database. 15

16 Reconfiguring the database connection file To allow users to connect to the SQL Server 2005 or 2008 version of the database, you must reconfigure the connection file to point to the destination server and database. This requires the following information: the path to the security connection file the path to the database connection file the user name and password of an ibase security administrator the SQL Server and instance name To reconfigure the database connection file: 1. Open the ibase 8 Database Configuration tool. From the Windows Start menu, select All Programs > IBM i2 ibase 8 > Tools > ibase Database Configuration. 2. Browse to the location of the security connection file that secures the database connection file you wish to reconfigure. 3. Browse to the location of the database connection file you wish to reconfigure. 4. Enter values for the user name and password of an ibase security administrator for the security file and database. 5. Click Next to validate the user credentials. The connection configuration values are displayed. 6. Change the server name to that of the destination server. Notice that it is not possible to alter the SQL Server database name. 7. Ensure you turn on the Test connection before saving check box. Doing so will alert you to any configuration errors that are preventing a successful connection to the database. 8. Save the configuration details and test that your ibase users are able to log on to the database successfully, now that the connection file references the database on the destination server. Post migration steps Completing the migration On completion of the upgrade, bring the databases back online, and open the database using ibase Designer. The Full Text Search may be rebuilt if required. For information on rebuilding your Full Text Search index please refer to the ibase Designer Online Help. Once the changes made by ibase Designer have been completed, set the user access option on the SQL Server database to multi-user, and confirm that the users are able to access the databases successfully. 16

17 Additional actions for replicated databases Immediately after the publishing security file, database, and audit log have been migrated to SQL Server 2005 or 2008, your SQL Server DBA can reconfigure the publication on these databases. As soon as the publication has been created, you will be able to bring the publication database back online from within ibase, using the options on the Replication menu. This will allow nonadministrative users to access the publication database while still keeping users out of the subscriber databases until the SQL Server DBA has created their subscriptions. Administrative users will still be able to access the subscriber databases before the SQL Server DBA has subscribed to the publication. Care should be taken to ensure that no changes are made to the subscriber databases while they are still offline. The subscriber databases will automatically be brought online with the creation of the subscription. Additional actions for users of ibase 8 Scheduler Restart the Scheduler service (or reactivate the Scheduler triggers if you chose to deactivate them), and then test that your scheduled imports and exports are working correctly. Additional actions for Analyst's Workstation client machines Through Data Miner, an Analyst's Workstation client machine can be configured to access any version of Microsoft SQL Server Analysis Server. To configure your client machine to access a SQL Server 2005 or 2008 Analysis Server, you must: Ensure that all prerequisites are installed (See Appendix A: Prerequisites for Analyst's Workstation). Note: Please refer to the System Requirements section of the IBM i2 Analyst s Workstation Release Notes for further information. Modify the Data Miner registry settings to enable Data Miner to build cubes on this instance of Microsoft SQL Server Analysis Server. Note: Please refer to the topic Specifying which Analysis Server to Use for Cube Building in the Administration Center for further information. Troubleshooting SQL Server Upgrade Advisor Microsoft provides a reporting tool that will alert you to potential issues with your upgrade. This is available online, and can be run before performing the upgrade to highlight any potential issues. Hard Disk Space Requirements During the upgrade process of SQL Server 2005 or 2008, Windows Installer creates temporary files on the system drive. You should ensure that you have sufficient temporary disk space available before starting the upgrade process. Note: The hard disk space requirements depend on your system configuration and on the amount of data present in your database. 17

18 Restoring ibase files and SQL Server databases If the upgrade fails, to roll back the process: 1. Restore all SQL Server ibase databases, ibase audit log databases, and ibase security file databases overwriting the partially upgraded databases. Database compatibility levels 2. Restore all.ids,.idb,.idl and.idx files. Upgrading SQL Server using the backup and restore migration method, will fail to change the database compatibility mode. Refer to Ensuring that you are running in the correct SQL compatibility mode for details of how to change this. SQL Server password strength The SQL Server database administrator (DBA) password policy was strengthened in SQL Server 2005 and this change enforced in SQL Server 2008 and later versions. To prevent access problems, we advise you to ensure that your password is strong before beginning the upgrade process. Audit log databases When an ibase database is migrated to SQL Server 2005 or 2008 using the backup and restore method, you must ensure that any audit log database is restored at the same time as the main database. Unicode database names Databases that have a Unicode name will not be able to set the SQL server compatibility level. If you have a database with a Unicode name, please contact support. Full text indexes The upgrade process will not succeed if any Full Text Indexes are present. These should be removed before starting the upgrade. Alerting Alerting should be disabled before starting an SQL Server upgrade. 18

19 Appendix A: Prerequisites for Analyst s Workstation The following SQL components (provided with the product) must be installed on each client machine to access the Analysis Server. SQL Server 2005 or Microsoft SQL Server 2005 Backward Compatibility Components Decision Support Objects 2. Microsoft SQL Server Native Client 3. Microsoft SQL Server 2005 Management Objects Collection Hot Fix KB Microsoft Core XML Services (MSXML) Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider 6. Microsoft SQL Server 2005 Analysis Services ADOMD.NET Note: The prerequisites should be installed in the order listed above. Appendix B: Additional information What documentation is provided? To help you get the most from your investment, ibase 8 is provided with comprehensive help and release notes. Administrators using ibase 8 Designer are supported by a comprehensive online Administration Center that specifically addresses information needed for database configuration, maintenance and performance. The help is supported by an example database and (where appropriate) sample data. Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, 19

20 EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM United Kingdom Limited Hursley House Hursley Park Winchester, Hants, SO21 2JN UK Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. 20

21 Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. ArcGIS, EDN, and are trademarks, registered trademarks, or service marks of Esri in the United States, the European Community, or certain other jurisdictions. Other names may be trademarks of their respective owners. Other company, product, and service names may be trademarks or service marks of others. 21