Siemens Teamcenter Oracle -to-sql Server 2008 Migration Guide

Size: px
Start display at page:

Download "Siemens Teamcenter Oracle -to-sql Server 2008 Migration Guide"

Transcription

1 Siemens Teamcenter Oracle -to-sql Server 2008 Migration Guide Microsoft Corporation Published: June 2010 Author: Randy Dyess Solid Quality Mentors Technical Reviewers: Christopher Gill Teamcenter Centers of Excellence, Siemens PLM Software Hewat Kennedy Siemens Abstract This white paper outlines a best practices methodology to use when migrating from a Siemens Teamcenter Oracle installation to Siemens Teamcenter running on the Microsoft SQL Server 2008 database platform.

2 2

3 Copyright Information The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in, or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property Microsoft Corporation. All rights reserved. Microsoft, SQL Server, and Windows are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners. 3

4 Table of Contents Siemens Teamcenter Oracle -to-sql Server 2008 Migration Guide... 1 About This Guide... 5 Overview of the Teamcenter Oracle-to-SQL Server Migration Process... 5 Creating the Migration Plan for a Teamcenter Migration... 6 Installing the Teamcenter SQL Server Database... 6 Installing the Oracle Client Creating a Linked Server Installing SQL Server Migration Assistant for Oracle V Determining Teamcenter Customizations Migrating the Data into the Teamcenter Database Performing Post-Migration Tasks Validating the Migration Through Teamcenter Use Cases Appendix A: Basic Data Type Conversions Appendix B: Sample Teamcenter Table Creation Scripts Appendix C: Links for Further Information

5 About This Guide The Siemens Teamcenter Oracle -to-sql Server 2008 Migration Guide describes how to migrate Teamcenter data from an Oracle database to a Microsoft SQL Server 2008 database. This guide is intended for technical staff members who are experienced in application installations and familiar with the installation hardware system. The Oracle-to-SQL Server migration process assumes an entry-level database administration skill level for both Oracle and SQL Server databases. Related Documentation The following documentation may be helpful in learning more about implementing Teamcenter on SQL Server: Siemens PLM-Related Documents o Installation on Windows Servers Guide o Business Modeler IDE Guide o Best Practices for Running Siemens Teamcenter on SQL Server Overview of the Teamcenter Oracle-to-SQL Server Migration Process The overall objective of the migration process is to extract the Teamcenter data from an Oracle database to a SQL Server 2008 database. The migration of an existing Teamcenter Oracle database to SQL Server involves multiple steps using both supplied PL/SQL and Transact-SQL (T-SQL) scripts and the downloadable SQL Server Migration Assistant (SSMA) 2008 for Oracle V4.0. You use the supplied scripts to determine and adjust the schema of an empty SQL Server Teamcenter database to match that of the existing Oracle database. After the schema is adjusted, you use the SSMA tool to migrate the data. The primary steps involved in the migration process are as follows: 1. Create a migration plan that includes a recovery strategy in case of failure and use-case scenarios to test data correctness. 2. Install a default production installation of SQL Server that includes all components currently installed on your Oracle instance on a new server and then create a Teamcenter SQL Server database. 3. Back up both the production SQL Server and the Oracle databases. 4. Create an empty SQL Server database called INFODBA for data staging. 5. Create copies of the PPOM_ATTRIBUTES and PPOM_CLASS and tables in the production database on the staging database. 6. Delete any existing data in the production SQL Server database. 7. Install the Oracle Client. 8. Create a SQL Server linked server to Oracle from the staging database. 9. Install the SQL Server Migration Assistant for Oracle and SSMA Extension Pack on your SQL Server server 10. Migrate the schema from Oracle to the SQL Server staging database using SSMA. 11. Adjust the schema of the SQL Server staging database to allow for data movement. 5

6 12. Migrate the data from the Oracle database to the staging database using T-SQL scripts through the linked server. 13. Create a backup of the staging database. 14. Create a database snapshot of the staging database. 15. Execute object and column rename scripts against the staging database. 16. Migrate the data from the staging database to the production database using T-SQL scripts. 17. Perform post-migration tasks using the supplied scripts and SQL Server Management Studio. 18. Validate the success of the migration with use-case scenarios. 19. Back up both the production SQL Server database. Creating the Migration Plan for a Teamcenter Migration A good migration plan is simple yet encompasses the appropriate steps to help ensure a successful migration. The migration plan should list dates, times, staff, testing procedures, recovery options, and validation procedures to be used during and after the migration of the database. A migration plan should answer the following questions: Who is going to build the new server and install Windows and SQL Server? When is the due date for the new server build-out? Who is going to install Teamcenter and create the new SQL Server Teamcenter database? When is the due date for the database? Who will verify the SQL Server installation and Teamcenter database against the Teamcenter on SQL Server installation guidelines? Does the migration process require an Oracle DBA as well as a SQL Server DBA? Will you need to hire an outside firm to help with the migration? What DBA and development resources do you have to test and perform the migration? What are the migration testing options new server or existing server? When should all migration testing be finished? What is the date for the actual migration? Will all required staff be available on the migration date? How much downtime will be required for the migration? What is the plan if the new database is not available due to issues during the migration? During the creation of your migration plan, you will also need to determine several use cases to use in testing against your migrated database. As you can see from these bullet points, a migration plan does not have to be overly complex. However, you will need to answer some essential questions, document those answers, and then combine those answers with the steps contained in this document. Installing the Teamcenter SQL Server Database There are no special requirements for installing SQL Server on your new server or creating the SQL Server database for the migration. However, you should follow all guidelines for installing and using 6

7 Teamcenter with a SQL Server database as described in the Siemens Teamcenter 8 Installation on Windows Server Guide. Any additional requirements are listed in the following sections of this white paper. If you know the customizations you have made to your Oracle database and can recreate those customizations in your SQL Server database, you should do so before the migration process to speed the process and reduce its complexity. After installing SQL Server and creating the database for the migration, you need to change the recovery model of the SQL Server Teamcenter database to Simple for the migration process. After the migration process, you will need to set the recovery model back to Full. 1. To change the recovery model, open SQL Server Management Studio (SSMS) by going to Start, All Programs, Microsoft SQL Server 2008, SQL Server Management Studio. 2. Connect to your instance. 3. In the Object Explorer, expand the instance and then expand the Databases folder. 7

8 4. Right-click your database and choose Properties. 5. Change to the Options Page on the right, and use the Recovery model drop-down box to change the recovery model to Simple. After changing the database to the Simple recovery model, right-click the database again and select Tasks. Select Back Up and create a backup of your database. You should also Export your Oracle database at this time. Next, you should create a SQL Server staging database called INFODBA, which will allow you to make any needed schema changes and test those changes before migrating the changed schema and data to your actual database: CREATE DATABASE INFODBA 8

9 Note: The above CREATE DATABASE script uses the model database to create a simple database. You will need to adjust the script to create a database on different directories than the model for your own installations. Or you can use SSMS to create the database. You also need to set the recovery model of the staging database to the Simple recovery model: After you create your SQL Server staging database, you need to capture the PPOM_CLASS and PPOM_ATTRIBUTES tables from your production database into your staging database in order to rename tables and columns later in the migration process. Simply execute the following script against your SQL Server database to save a copy of these tables in your staging database: USE INFODBA -- Change to your staging database SELECT * INTO PPOM_CLASS_saved FROM tc..ppom_class SELECT * INTO PPOM_ATTRIBUTE_saved FROM tc..ppom_attribute After the two needed tables, you need to empty any pre-populated tables in the production SQL Server database. You can accomplish by truncating all tables that contain data. Simply execute the following script against your SQL Server database to build the table truncate statements and then execute the results of the scripts: USE tc -- Change to your production database INT NVARCHAR(4000) BEGIN TRY DROP TABLE #commands END TRY BEGIN CATCH END CATCH CREATE TABLE #commands ( colid INT IDENTITY(1,1),command NVARCHAR(4000) 9

10 ) INSERT INTO #commands (command) SELECT 'TRUNCATE TABLE dbo.' + so.name FROM sys.partitions sp INNER JOIN sys.objects so ON sp.object_id = so.object_id WHERE sp.rows > 0 AND so.is_ms_shipped = 0 AND so.type = 'u' AND sp.index_id IN (0,1) ORDER BY so.name = > 0 BEGIN = command FROM #commands WHERE colid exec END -= 1 (Note: DO NOT delete any data in your existing Oracle production database.) Installing the Oracle Client To migrate the data between Oracle and SQL Server 2008, you need to install the latest Oracle Client software on your SQL Server 2008 server, as follows. 1. Obtain the latest Oracle Client (the version found at the at the download site is an example and may be different from the one you will need to obtain and install): Then accept the License Agreement. 2. Make sure you download the correct version of the client. Note: This whitepaper refers to the x64 10g release; your version may be different. 10

11 11

12 3. Unzip the saved file and execute Setup.exe to start the installation. 12

13 4. Choose to install the InstantClient. 13

14 5. Enter the Home Destination details, which specify the name for the installation and the path where you want the client installed, and click Next. 14

15 6. Correct any issues that the Installer finds. 15

16 7. Click Install to install the client. 16

17 17

18 8. When the installation process is complete, simply exit the Installer. 18

19 Creating a Linked Server One of the easiest methods to compare two different databases is through the use of a linked server. Using a SQL Server linked server allows you to directly compare the objects in your Oracle database to the objects in your SQL Server database. This will enable you to capture all missing objects and recreate them in SQL Server. Here are the steps for creating a linked server: 1. Open SSMS by going to Start, All Programs, Microsoft SQL Server 2008, SQL Server Management Studio. 2. Open the Server Objects folder in the object tree. 3. Right-click Linked Servers New Linked Server. 4. Create a new linked server by providing a name and data source details (note your connection may be different from this example). 19

20 5. Click the Security Tab and input the login and password you will use to connect to the Oracle database. (This example recreates the infodba login on SQL Server to use for the linked server: infodba with password of infodba. This login should be made a member of the dbo_owners group.) 6. Click OK, and then Test your new linked server by expanding the tables of the linked server. 20

21 21

22 Installing SQL Server Migration Assistant for Oracle V4.0 SQL Server Migration Assistant (SSMA) 2008 for Oracle is a suite of tools that reduces the effort, cost, and risk of migrating from Oracle to SQL Server Follow these instructions for installing SSMA: 1. Download SSMA V4.0 and the Extension pack to your SQL Server server here. 2. Unzip the downloaded file and double-click the SSMA installer, SSMA 2008 for Oracle.4.0.Install.exe, and at the Welcome screen click Next. 22

23 3. Accept the License Agreement and click Next. 4. Determine if you want to send a Usage Report to Microsoft and then click Next. 23

24 5. Choose the Typical installation. 6. Click Install. 24

25 7. When the installation is complete, click Finish. 8. You re not ready to install the Extension Pack by unzipping the downloaded file and doubleclicking the SSMA installer called SSMA 2008 for Oracle Extension Pack.4.0.Install.exe. 25

26 9. At the Welcome screen, click Next. 10. Accept the License Agreement and click Next. 26

27 11. Again, choose the Typical installation option. 27

28 12. Click Install to begin the installation. 28

29 13. When the first step of the installation is complete, click Next to install SQL scripts on the instances you specify. 29

30 14. Choose the SQL Server database instance (your instance name will be different from the example) and click Next. 30

31 15. Enter the connection information required to connect to your SQL Server database instance and click Next. 31

32 16. At the screen that asks whether you would like to install the Extension Pack Utilities Database on your instance, leave at the default settings to install them and click Next. 17. The installation will run and execute several scripts. 32

33 18. After the installation is finished, click No; you do not want to install the Utilities Database on another instance. 33

34 Configuring SQL Server to Use SQLCLR After installing SSMA and the SSMA extension pack, you need to configure the SQL Server instance to utilize the SQL Server Common Language Runtime (SQLCLR). 1. Open a new query window using SSMS and execute the following script to enable CLR in the SQL Server instance: EXEC sp_configure 'clr enabled',1 reconfigure Installing the SSMA License Key You are now ready to install the SSMA license key. 1. Start SSMA from the Start menu. 34

35 2. Obtain the License Key by using the provided license registration page link. Note: You will need to register with Microsoft to obtain the license key. This registration is used to help provide support for SSMA and notify you of SSMA updates and fixes. 3. Save the license file. 35

36 4. Change the directory to the location where you placed the downloaded license key and refresh the license. 36

37 Determining Teamcenter Customizations Teamcenter allows for the addition of features and functionalities beyond the base installation. These new features and functionalities often create new database objects in the Teamcenter database. To maintain your existing data in the migration, you need to add these new components to your SQL Server installation of Teamcenter after the base installation of Teamcenter is complete. Your SQL Server database schema will then be as close to your Oracle database as possible. If you have objects in your Oracle database that have not been created in the SQL Server installation, it is important to capture these new objects and recreate them in the destination SQL Server database. Capturing the new objects created through customizations is achieved by reading the Oracle metadata tables and comparing the existing Oracle tables, constraints, and indexes with those found in the SQL Server database. After the comparisons are made, you need to script out the objects and create them in your SQL Server 2008 production database. To ease the migration effort, SSMA is used to create the schema in a staging database for the initial migration to SQL Server. This converted schema will then be used to compare to the production database to identify missing objects. Note: Teamcenter provides the functionality to automatically create needed indexes on Teamcenter database objects. If you have custom objects not created through the Teamcenter application, you need to manually recreate those objects in your Teamcenter SQL Server database. For objects created through Teamcenter, Teamcenter offers functionality that will recreate the indexes on those objects. Migrating the Teamcenter Schema to the Staging Database 1. Start SSMA by going to Start, All Programs, Microsoft SQL Server Migration Assistant for Oracle, Microsoft SQL Server Migration Assistant for Oracle. 2. Start a new project in SSMA by clicking New Project and then giving the project a name and location. 37

38 38

39 3. Connect to the Oracle database. 5. Expand the INFODBA schema and select Tables. 6. Choose the Type Mapping tab to edit the default mappings. 39

40 7. Edit the following mappings as noted by highlighting the data type and clicking Edit. Source Type Float Number Numeric Real Target Type Float Float Float Float 40

41 8. Click OK and repeat for each data type in the above table. 9. Now connect to the SQL Server database. 10. Expand the SQL Server database. 41

42 11. Highlight the Oracle schema to be converted. 12. Click the Convert Schema tab. 13. Reconnect to the Oracle database. 14. The SSMA will analyze the metadata and create the conversion files. 15. When the analysis is finished, you will see that the output shows both errors and warnings. The 23 errors are for function-based indexes, and the warnings are for loss of precision. The indexes 42

43 have been accounted for in the production schema, and we are not using SSMA to migrate the data. You can ignore these errors and warnings. Note: Your exact output may be different depending on the amount of customizations you have to your Oracle Teamcenter installation. 16. Once the conversion is finished, you need to synchronize the SQL Server database with the Oracle database by right-clicking the SQL Server database and selecting Synchronize with Database. 17. Click OK. 43

44 18. Because the INFODBA database is a staging database, the indexes are not needed. To speed the data migration process, you should drop all indexes in the staging database. Execute the following script in SSMS to create your index drop statements, and then execute the results of the script to drop the indexes: USE INFODBA TABLE(colid INT IDENTITY(1,1),commandstr VARCHAR(2000)) NVARCHAR(2000) INT INSERT (commandstr) SELECT 'DROP INDEX ' + si.name + ' ON ' + so.name FROM sys.indexes si INNER JOIN sys.objects so ON si.object_id = so.object_id WHERE so.is_ms_shipped = 0 AND si.index_id > 0 = > 0 BEGIN = commandstr WHERE colid 44

45 BEGIN TRY EXEC END TRY BEGIN CATCH END CATCH END -= 1 Determining Table Object Differences To determine schema object differences, use the following script to compare the schema created by SSMA in the INFODBA database with the schema from the production SQL Server database: USE INFODBA SELECT TABLE_NAME FROM ORACLETC..SYS.USER_TABLES WHERE TABLE_NAME NOT IN (SELECT name COLLATE Latin1_General_BIN FROM sys.objects WHERE type = 'u' AND is_ms_shipped = 0) AND TABLE_NAME <> 'PLAN_TABLE' ORDER BY TABLE_NAME Execute the results of the above script to identify tables that you will need to create. Once you have a list of tables that are missing from the SQL Server database, you need to connect to Oracle to describe the tables so that you can recreate them in SQL Server. Do not use the schema created by SSMA to recreate the missing tables; use the Oracle schema. In Oracle For each table in the output from the above script, describe the table and create a T-SQL table creation script for the table. For example, let s say that the PCOUNTER_TAGS_1 table was not found in SQL Server. To get the description, execute the following: desc PCOUNTER_TAGS_1; The output is as follows: Name Null? Type PUID NOT NULL VARCHAR2(15) PSEQ NOT NULL NUMBER(38) PVALU_0 VARCHAR2(15) PVALC_0 NUMBER(38) This output of the table description will translate into the SQL Server CREATE TABLE statement below (using lower case for column names): 45

46 Note: Use the SQL Server-to-Oracle data type conversion table in Appendix A to correctly map the data types from Oracle to SQL Server. BEGIN TRY DROP TABLE PCOUNTER_TAGS_1 END TRY BEGIN CATCH END CATCH CREATE TABLE PCOUNTER_TAGS_1 ( puid NVARCHAR(15) NOT NULL,pseq FLOAT NOT NULL,pvalu_0 NVARCHAR(15),pvalc_0 FLOAT ) Note: You can find sample CREATE TABLE scripts in Appendix B for creating tables missing from base installations. In SQL Server Execute the CREATE TABLE statements you created for each missing Oracle table in your production database. Determining Index Object Differences After identifying and creating missing table objects, you need to create any indexes for those missing table objects. You can use the Teamcenter index tool (index_verifier) to recreate any missing indexes in your production database. You do not need to create indexes in your staging database. Determining Constraint Object Differences After determining and creating missing table objects, you need to create any constraints for those missing table objects. --This script will determine difference in constraints SELECT * FROM ORACLETC..SYS.USER_CONSTRAINTS WHERE TABLE_NAME IN ('PCOUNTER_TAGS_1','SYS_IMPORT_SCHEMA_01','PFIXED_COST_TAGLIST_0','POM_UID_SCRATCH','PREFAUNIQUEEXPRID2','PVISSTRUCTURERECEIPE','PVISMANAGEDDOCUMENT','PPATTERN_0','POCCURRENCE_LIST','PVISSTRUCTURECONTEXT','PJTCONTENTFORMSTORAGE','EIM_UID_GENERATOR_ROOT') 46

47 ORDER BY TABLE_NAME; Now you can create those missing constraints on your tables in your production SQL Server production database: -- Change to your production database USE tc CREATE UNIQUE NONCLUSTERED INDEX SYS_C ON SYS_IMPORT_SCHEMA_01(PROCESS_ORDER,DUPLICATE) Note: You do not need to recreate NOT NULL constraints Migrating the Data into the Teamcenter Database After you have recreated all missing tables, indexes, and constraints, you are ready to migrate the data from the Oracle database into your staging database (INFODBA) in SQL Server. To migrate the data, you need to create a series of INSERT INTO statements to read the data from the Oracle tables into the SQL Server staging tables. Once you have moved the data into the staging tables, you will then move the data into the production SQL Server tables. Note: Appendix B provides some common table creation scripts. 1. Execute the following script to move the data into the staging database: USE INFODBA SET NOCOUNT ON BIGINT VARCHAR(255) nvarchar(4000) VARCHAR(4000) BEGIN TRY DROP TABLE #tables END TRY BEGIN CATCH END CATCH CREATE TABLE #tables ( colid INT IDENTITY(1,1),table_name VARCHAR(255) ) BEGIN TRY DROP TABLE #columns END TRY BEGIN CATCH 47

48 END CATCH CREATE TABLE #columns ( colid INT IDENTITY(1,1),column_name VARCHAR(255),system_type_id INT ) INSERT INTO #tables (table_name) SELECT TABLE_NAME FROM ORACLETC..SYS.USER_TABLES WHERE TABLE_NAME <> 'PLAN_TABLE' = > 0 BEGIN TRUNCATE TABLE #columns = table_name FROM #tables WHERE colid = 'INSERT INTO #columns (column_name,system_type_id) SELECT name, system_type_id FROM sys.columns WHERE object_id = OBJECT_ID(''' + ''')' EXEC UPDATE #columns SET column_name = 'CAST(' + column_name + ' AS VARCHAR(1000))' WHERE system_type_id IN (108) = '' + column_name + ',' FROM #columns + ' ' --take care of trailing comma = REPLACE ',' ') = 'INSERT INTO ' + ' SELECT * FROM OPENQUERY(ORACLETC,''SELECT ' + ' FROM INFODBA.' + ''') AS ROWSET_1' BEGIN TRY EXEC END TRY BEGIN CATCH END CATCH END -= 1 2. Verify that the rows in the Oracle database and the SQL Server staging database are consistent: 48

49 USE INFODBA SET NOCOUNT ON BEGIN TRY DROP TABLE #ora_tables END TRY BEGIN CATCH END CATCH CREATE TABLE #ora_tables ( colid INT IDENTITY(1,1),table_name VARCHAR(255),row_count BIGINT ) BEGIN TRY DROP TABLE #sql_tables END TRY BEGIN CATCH END CATCH CREATE TABLE #sql_tables ( colid INT IDENTITY(1,1),table_name VARCHAR(255),row_count BIGINT ) INT INT VARCHAR(255) NVARCHAR(4000) INSERT INTO #sql_tables(table_name) SELECT name FROM sys.objects WHERE is_ms_shipped = 0 AND type = 'U' = > 0 BEGIN = table_name FROM #sql_tables WHERE colid END = 'UPDATE #sql_tables SET row_count = (SELECT COUNT(*) FROM dbo.' + ' WITH (NOLOCK)) WHERE colid = ' + AS VARCHAR(20)) EXEC -= 1 INSERT INTO #ora_tables(table_name) SELECT TABLE_NAME FROM ORACLETC..SYS.USER_TABLES = 49

50 > 0 BEGIN = table_name FROM #ora_tables WHERE colid END = 'UPDATE #ora_tables SET row_count = (SELECT COUNT(*) FROM dbo.' + ' WITH (NOLOCK)) WHERE colid = ' + AS VARCHAR(20)) EXEC -= 1 --Tables showing up have different row counts SELECT sc.table_name AS 'Staging Table',sc.row_count AS 'Staging row count',oc.table_name AS 'Oracle Table',oc.row_count AS 'Oracle row count' FROM #sql_tables sc INNER JOIN #ora_tables oc ON sc.table_name = oc.table_name AND sc.row_count <> oc.row_count 3. Verify that the data precision is the same: USE INFODBA SET NOCOUNT ON BEGIN TRY DROP TABLE #ora_tables END TRY BEGIN CATCH END CATCH CREATE TABLE #ora_tables ( colid INT IDENTITY(1,1),table_name VARCHAR(255),column_name VARCHAR(255),ora_data_length INT,sql_data_length INT ) INT INT VARCHAR(255) VARCHAR(255) NVARCHAR(4000) = 1 INSERT INTO #ora_tables(table_name,column_name) SELECT TABLE_NAME, COLUMN_NAME FROM ORACLETC..SYS.USER_TAB_COLUMNS WHERE DATA_TYPE = 'FLOAT' AND DATA_PRECISION = 126 = 50

51 > 0 BEGIN = = column_name FROM #ora_tables WHERE colid END = 'UPDATE #ora_tables SET ora_data_length = (SELECT ISNULL(MAX(LEN(' + ')),0) FROM ORACLETC..INFODBA.' + ' WITH (NOLOCK)) WHERE colid = ' + AS VARCHAR(20)) EXEC -= 1 > 0 BEGIN = = column_name FROM #ora_tables WHERE colid END = 'UPDATE #ora_tables SET sql_data_length = (SELECT ISNULL(MAX(LEN(' + ')),O) FROM dbo.' + ' WITH (NOLOCK)) WHERE colid = ' + AS VARCHAR(20)) EXEC -= 1 --Should be no result set SELECT * FROM #ora_tables WHERE ora_data_length <> sql_data_length Note: You may have to manually correct any data precision issues by changing the data types of the production SQL Server database. 4. After migrating the data from the Oracle database into your staging database, create a backup of the staging database. 5. After the backup completes, you will need to create a snapshot database of the database for easier rollback to the migrated staging database in case of errors or issues during the migration to the production database. USE master --Determine file names SELECT name, physical_name FROM sys.master_files WHERE database_id = DB_ID('INFODBA') CREATE DATABASE INFODBA_snapshot ON --You will need to change the path to your SQL Server directory. 51

52 ( NAME = INFODBA, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Data\INFODBA.ss' ) AS SNAPSHOT OF INFODBA; 6. After creating a snapshot of the staging database for rollback purposes, you will now need to rename several tables in the staging database schema to match the production database schema. --Rename tables in staging to match production USE INFODBA SET NOCOUNT ON INT INT INT NVARCHAR(4000) NVARCHAR(4000) --There will be one set of commands for temporary names --There will be another set of commands for final names = 2 --Table to hold rename commands BEGIN TRY DROP TABLE #PLOVP END TRY BEGIN CATCH END CATCH CREATE TABLE #PLOVP ( colid INT IDENTITY(1,1),command_1 NVARCHAR(4000) COLLATE Latin1_General_BIN,command_2 NVARCHAR(4000) COLLATE Latin1_General_BIN ) --Determine the difference between SQL Server version and Oracle version --Rename to SQL Server version --Need to set tables to temp names to avoid renaming conflicts INSERT INTO #PLOVP (command_1, command_2) SELECT 'exec sp_rename ''' + infodba.pdbname COLLATE Latin1_General_BIN + ''',''' + tc.pdbname + '_new''','exec sp_rename '''+ tc.pdbname + '_new'''+ ',''' + tc.pdbname + '''' FROM (SELECT a.pdbname,c.pname AS pname_class,a.pname AS pname_attribute FROM INFODBA..PPOM_CLASS_saved c INNER JOIN INFODBA..PPOM_ATTRIBUTE_saved a ON a.rdefining_classu = c.puid AND a.plength = -1 52

53 WHERE a.pdbname LIKE 'PLOV_VALUES%') tc INNER JOIN (SELECT a.pdbname,c.pname AS pname_class,a.pname AS pname_attribute FROM INFODBA..PPOM_CLASS c INNER JOIN INFODBA..PPOM_ATTRIBUTE a ON a.rdefining_classu = c.puid AND a.plength = -1 WHERE a.pdbname LIKE 'PLOV_VALUES%' AND c.pname LIKE 'ListOf%') infodba ON tc.pname_class = infodba.pname_class COLLATE Latin1_General_BIN AND tc.pname_attribute = infodba.pname_attribute COLLATE Latin1_General_BIN = > 0 BEGIN --Execute rename statements > 0 BEGIN = = command_2 FROM #PLOVP WHERE colid = 2 BEGIN EXEC END = 1 BEGIN EXEC END END -= 1 END -= 1 7. After creating a snapshot of the staging database for rollback purposes, you will now need to rename several columns in the staging database schema to match the production database schema. --Rename columns in staging to match production USE INFODBA SET NOCOUNT ON INT NVARCHAR(4000) --Table to hold rename commands 53

54 BEGIN TRY DROP TABLE #PLOVP END TRY BEGIN CATCH END CATCH CREATE TABLE #PLOVP ( colid INT IDENTITY(1,1),command_1 NVARCHAR(4000) COLLATE Latin1_General_BIN ) --Determine the column naming differences between SQL Server version and Oracle version --Rename to SQL Server version INSERT INTO #PLOVP (command_1) SELECT 'EXEC dbo.sp_rename ''' + info.tabname_class + '.' + info.vla + ''',''' + tc.vla + ''',''COLUMN''' FROM (SELECT 'VLA_'+ CONVERT(VARCHAR, pc.pcpid) + '_' + CONVERT(VARCHAR, pa.papid) AS vla,pc.pname AS oname,pa.pname AS descp,pc.ptname AS tabname_class FROM INFODBA..PPOM_CLASS pc INNER JOIN INFODBA..PPOM_ATTRIBUTE pa ON pa.rdefining_classu = pc.puid AND pa.plength = -1) info INNER JOIN (SELECT 'VLA_'+ CONVERT(VARCHAR, pc.pcpid) + '_' + CONVERT(VARCHAR, pa.papid) AS VLA,pc.PNAME AS oname,pa.pname AS descp,pc.ptname AS tabname_class FROM INFODBA..PPOM_CLASS_saved pc INNER JOIN INFODBA..PPOM_ATTRIBUTE_saved pa ON pa.rdefining_classu = pc.puid AND pa.plength = -1) tc ON info.oname COLLATE Latin1_General_BIN = tc.oname AND info.descp COLLATE Latin1_General_BIN = tc.descp AND info.tabname_class COLLATE Latin1_General_BIN = tc.tabname_class = > 0 BEGIN = command_1 FROM #PLOVP WHERE colid BEGIN TRY EXEC END TRY BEGIN CATCH END CATCH END -= 1 54

55 8. Update columns in the POM_INDEXES table. --Determine and rename duplicate entries USE INFODBA UPDATE TOP (1) d SET d.dbname = d.dbname + '_' + CAST(d.youneek AS VARCHAR(11)) FROM POM_INDEXES d INNER JOIN ( SELECT dbname,cpid,apid FROM POM_INDEXES GROUP BY dbname,cpid,apid HAVING COUNT(*) > 1)db ON db.dbname = d.dbname AND db.cpid = d.cpid AND db.apid = d.apid 9. Drop the temporary PPOM_CLASS_saved and PPOM_ATTRIBUTE_saved tables. USE INFODBA DROP TABLE PPOM_CLASS_saved DROP TABLE PPOM_ATTRIBUTE_saved 10. Once you are satisfied that everything is correct and have performed all use-case testing from your migration plan, migrate the data into the production database: USE tc SET NOCOUNT ON BIGINT VARCHAR(255) nvarchar(4000) VARCHAR(4000) BEGIN TRY DROP TABLE #row_count END TRY BEGIN CATCH END CATCH CREATE TABLE #row_count ( colid INT IDENTITY(1,1),table_name VARCHAR(255),row_count BIGINT ) 55

56 BEGIN TRY DROP TABLE #tables END TRY BEGIN CATCH END CATCH CREATE TABLE #tables ( colid INT IDENTITY(1,1),table_name VARCHAR(255) ) BEGIN TRY DROP TABLE #columns END TRY BEGIN CATCH END CATCH CREATE TABLE #columns ( colid INT IDENTITY(1,1),column_name VARCHAR(255),system_type_id INT ) INT INSERT INTO #row_count(table_name) SELECT name FROM INFODBA.sys.objects WHERE is_ms_shipped = 0 AND type = 'U' = > 0 BEGIN = table_name FROM #row_count WHERE colid = 'UPDATE #row_count SET row_count = (SELECT COUNT(*) FROM INFODBA.dbo.' + ' WITH (NOLOCK)) WHERE colid = ' + AS VARCHAR(20)) EXEC -= 1 END INSERT INTO #tables (table_name) SELECT so.name FROM tc.sys.objects so WHERE so.is_ms_shipped = 0 AND so.type = 'U' = > 0 BEGIN TRUNCATE TABLE #columns = 0 56

57 = table_name FROM #tables WHERE colid = row_count FROM #row_count WHERE table_name = > 0 BEGIN = 'INSERT INTO #columns (column_name) SELECT name FROM tc.sys.columns WHERE object_id = OBJECT_ID(''' + ''')' EXEC = '' + column_name + ',' FROM #columns + ' ' --take care of trailing comma = REPLACE ',' ') + = 'INSERT INTO ' + '(' + ' SELECT ' + ' FROM INFODBA.dbo.' + BEGIN TRY EXEC END TRY BEGIN CATCH AS 'Table did not load investigate manually' END CATCH END -= 1 END 11. The script above will produce a listing of tables that did not have data into them due to column differences between the staging and production databases. You may have to manually create some table insert statements to overcome these column differences, as in these examples: USE tc --Column names different INSERT INTO PPOM_SITE_CONFIG(puid,LS_13_2,pindex ) SELECT puid,ls_388_1,pindex FROM INFODBA.dbo.PPOM_SITE_CONFIG --Column names different INSERT INTO PTC_PREFERENCES(puid,LS_330_2,robject_tagu,robject_tagc ) SELECT puid,ls_473_1,robject_tagu,robject_tagc FROM INFODBA.dbo.PTC_PREFERENCES 57

58 --Column names are different INSERT INTO PFULLTEXT(puid,LS_739_1,pbody_cleartext,pcontent_type ) SELECT puid,ls_492_1,pbody_cleartext,pcontent_type FROM INFODBA.dbo.PFULLTEXT --Column PIPLISTOFVALUES_1_0 not in SQL Server table INSERT INTO PLISTOFVALUES(puid,plov_name,plov_desc,plov_type,plov_attached_class,pl ov_attached_attr,vla_427_9,vla_427_10,vla_427_11,vla_427_12,vla_427_13, VLA_427_14,VLA_427_15,VLA_427_16,VLA_427_17,VLA_427_18,VLA_427_19,VLA_4 27_20,plov_attached_type,plov_value_type,plov_usage ) SELECT puid,plov_name,plov_desc,plov_type,plov_attached_class,plov_attached_at tr,vla_427_9,vla_427_10,vla_427_11,vla_427_12,vla_427_13,vla_427_14,vla _427_15,VLA_427_16,VLA_427_17,VLA_427_18,VLA_427_19,VLA_427_20,plov_att ached_type,plov_value_type,plov_usage FROM INFODBA.dbo.PLISTOFVALUES --Column PIPIMANQUERY_1_0 not in SQL Server table INSERT INTO PIMANQUERY(puid,pquery_name,pquery_desc,pquery_class,VLA_184_4,pquery_u id_name,pquery_flag,presults_type ) SELECT puid,pquery_name,pquery_desc,pquery_class,vla_184_4,pquery_uid_name,pqu ery_flag,presults_type FROM INFODBA.dbo.PIMANQUERY --Column PIPITEMREVISION_2_0 not in SQL Server table INSERT INTO PITEMREVISION(puid,pitem_revision_id,VLA_631_8,VLA_631_10,VLA_631_11,VL A_631_12,rsequence_anchoru,rsequence_anchorc,rvariant_expression_blocku,rvariant_expression_blockc,ritems_tagu,ritems_tagc,psequence_id,pseque nce_limit,phas_variant_module) SELECT puid,pitem_revision_id,vla_631_8,vla_631_10,vla_631_11,vla_631_12,rsequ ence_anchoru,rsequence_anchorc,rvariant_expression_blocku,rvariant_expr ession_blockc,ritems_tagu,ritems_tagc,psequence_id,psequence_limit,phas _variant_module FROM INFODBA.dbo.PITEMREVISION --Columns PIPOM_KEY_0 and PIPOM_KEY_1 not in SQL Server table INSERT INTO POM_KEY(puid,domain,key_value) SELECT puid,domain,key_value FROM INFODBA.dbo.POM_KEY --Column PIPPOM_USER_1_0 not in SQL Server table INSERT INTO PPOM_USER(puid,puser_id,ppassword,puser_name,pstatus,pdef_acl,pdefault_ group,puser_data_source,plicense_level,plast_login_time,puser_last_sync _date ) SELECT puid,puser_id,ppassword,puser_name,pstatus,pdef_acl,pdefault_group,puse r_data_source,plicense_level,plast_login_time,puser_last_sync_date FROM INFODBA.dbo.PPOM_USER --Column difference INSERT INTO POM_ROOT(site_id,[schema],[path],site_state,cpid,[version],scan_state,s can_name,scan_class,info,can_edit_schema ) 58

59 SELECT site_id,[schema],[path],site_state,cpid,[version],scan_state,scan_name, scan_class,info,can_edit_schema FROM INFODBA.dbo.POM_ROOT --Columns PIPWORKSPACEOBJ_0_0 and PIPWORKSPACEOBJ_1_0 not in SQL Server table INSERT INTO PWORKSPACEOBJECT(puid,pobject_name,pobject_desc,pobject_type,pobject_ap plication,vla_484_7,pip_classification,vla_484_10,pgov_classification,v LA_484_13,VLA_484_16,pactive_seq,prevision_number,rwso_threadu,rwso_thr eadc,rowning_organizationu,rowning_organizationc,prevision_limit,rownin g_projectu,rowning_projectc,pdate_released ) SELECT puid,pobject_name,pobject_desc,pobject_type,pobject_application,vla_484 _7,pip_classification,VLA_484_10,pgov_classification,VLA_484_13,VLA_484 _16,pactive_seq,prevision_number,rwso_threadu,rwso_threadc,rowning_orga nizationu,rowning_organizationc,prevision_limit,rowning_projectu,rownin g_projectc,pdate_released FROM INFODBA.dbo.PWORKSPACEOBJECT 12. Verify the row counts between the staging and production SQL Server databases: USE INFODBA SET NOCOUNT ON BEGIN TRY DROP TABLE #sql_tables_staging END TRY BEGIN CATCH END CATCH CREATE TABLE #sql_tables_staging ( colid INT IDENTITY(1,1),table_name VARCHAR(255),row_count BIGINT ) BEGIN TRY DROP TABLE #sql_tables_final END TRY BEGIN CATCH END CATCH CREATE TABLE #sql_tables_final ( colid INT IDENTITY(1,1),table_name VARCHAR(255),row_count BIGINT ) INT INT VARCHAR(255) NVARCHAR(4000) 59

60 INSERT INTO #sql_tables_staging(table_name) SELECT name FROM sys.objects WHERE is_ms_shipped = 0 AND type = 'U' = > 0 BEGIN = table_name FROM #sql_tables_staging WHERE colid END = 'UPDATE #sql_tables_staging SET row_count = (SELECT COUNT(*) FROM dbo.' + ' WITH (NOLOCK)) WHERE colid = ' + AS VARCHAR(20)) EXEC -= 1 INSERT INTO #sql_tables_final(table_name) SELECT name FROM tc.sys.objects --you will have to change to your database name WHERE is_ms_shipped = 0 AND type = 'U' = > 0 BEGIN = table_name FROM #sql_tables_final WHERE colid END = 'UPDATE #sql_tables_final SET row_count = (SELECT COUNT(*) FROM tc.dbo.' + ' WITH (NOLOCK)) WHERE colid = ' + AS VARCHAR(20)) EXEC -= 1 --Tables showing up have different row counts SELECT sc.table_name AS 'Staging Table',sc.row_count AS 'Staging Row Count',fc.table_name AS 'Production Table',fc.row_count AS 'Production Table Row Count' FROM #sql_tables_staging sc INNER JOIN #sql_tables_final fc ON sc.table_name = fc.table_name AND sc.row_count <> fc.row_count 13. Verify that the data precision is the same: USE INFODBA SET NOCOUNT ON BEGIN TRY 60

61 DROP TABLE #staging_tables END TRY BEGIN CATCH END CATCH CREATE TABLE #staging_tables ( colid INT IDENTITY(1,1),table_name VARCHAR(255),column_name VARCHAR(255),staging_data_length INT,final_data_length INT ) INT INT VARCHAR(255) VARCHAR(255) NVARCHAR(4000) = 1 INSERT INTO #staging_tables(table_name,column_name) SELECT TABLE_NAME, COLUMN_NAME FROM ORACLETC..SYS.USER_TAB_COLUMNS WHERE DATA_TYPE = 'FLOAT' AND DATA_PRECISION = 126 = > 0 BEGIN = = column_name FROM #staging_tables WHERE colid END = 'UPDATE #staging_tables SET staging_data_length = (SELECT ISNULL(MAX(LEN(' + ')),0) FROM INFODBA.dbo.' + ' WITH (NOLOCK)) WHERE colid = ' + AS VARCHAR(20)) EXEC -= 1 > 0 BEGIN = =LOWER(column_name) FROM #staging_tables WHERE colid --You will have to change production database name BEGIN TRY = 'UPDATE #staging_tables SET final_data_length = (SELECT ISNULL(MAX(LEN(' COLLATE Latin1_General_BIN + ')),0) FROM tc.dbo.' + ' WITH (NOLOCK)) WHERE colid = ' + AS VARCHAR(20)) EXEC END TRY BEGIN CATCH 61

62 END AS 'Table AS 'Column Name' END CATCH -= 1 --Should be no result set SELECT * FROM #staging_tables WHERE staging_data_length <> final_data_length Note; You may have to manually correct any data precision issues. 14. Drop the staging database snapshot: USE MASTER DROP DATABASE INFODBA_snapshot Performing Post-Migration Tasks After you have migrated and verified all your data, you need to perform the following post-migration tasks: 1. Index maintenance 2. Database checks 3. Database backups Monitoring Index Fragmentation and Defragmenting SQL Server uses indexes to provide fast access to information when users or applications request it. These indexes are maintained by the Database Engine as the table data grows and/or changes. Over time, the indexes can become fragmented; especially in databases that handle heavy insert, update, and delete activity. An index is fragmented when the physical ordering on disk does not match the logical order of the data (as defined by the index key) or when data pages that contain the index are dispersed across non-adjacent sections of the disk. Fragmentation of an index can reduce the speed of data access and result in slower application performance. It can also cause more disk space to be used than is actually necessary. Index fragmentation can be corrected by reorganizing or rebuilding the index. You can tell which indexes, if any, have fragmentation problems by using the sys.dm_db_physical_stats() system function. This function provides a lot of detail about the physical layout of the index. However, the most important result column for tracking fragmentation is avg_fragmentation_in_percent. This column indicates how fragmented the index is on disk. A low number means low fragmentation (good); a high number means high fragmentation (bad). For example, the following query returns index physical stats for all the indexes in the current database: 62

63 SELECT OBJECT_NAME(object_id), index_id, page_count, index_type_desc, avg_fragmentation_in_percent, fragment_count FROM sys.dm_db_index_physical_stats(db_id(),null,null,null,'limited') To identify the indexes by name, you can join against the sys.indexes system view. Similar information is also available in the Standard Reports in SSMS. To view this report, right-click the Teamcenter database, select Reports, Standard Reports, and then select the Index Physical Statistics report on the fly-out menu. The rule-of-thumb in the following table indicates how to interpret the avg_fragmentation_in_percent value. Fragmentation Recommended Action < 5% Do nothing 5% to 30% Reorganize with ALTER INDEX REORGANIZE > 50% Rebuild with ALTER INDEX REBUILD WITH (ONLINE=ON) or CREATE INDEX with DROP_EXISTING=ON Reorganizing an index does not block user access to the index while underway. Rebuilding or recreating the index, however, does prevent user access to the index. The exception to this is if the ALTER INDEX REBUILD statement is used with the ONLINE = ON option. Note that online index rebuild requires the Enterprise Edition of SQL Server Periodically checking index fragmentation and taking any necessary corrective action is important to maintaining the performance of your Teamcenter deployment. The rate at which fragmentation may occur depends on user activity, but as a general rule Siemens recommends checking index fragmentation at least monthly. Running the Teamcenter Index-Verifier Tool Siemens provides an index_verifier utility, packaged with all versions of Teamcenter, to analyze your Teamcenter database for missing indexes. If the index_verifier utility finds missing indexes, it will output SQL statements that you can use to create the indexes.siemens best practice is to run this utility monthly at a minimum. Siemens also recommends adding additional indexes you may require by using the install command-ine utility provided with Teamcenter. Doing so will register the index as part of the Teamcenter schema, at which point index_verifier can check for its existence. If you manually add indexes to the Teamcenter 63

64 database, index_verifier will have no knowledge of them and it will be your responsibility to ensure that those indexes are carried forward and maintained. You can find full documentation of these utilities in the Teamcenter Utilities Reference Manual available on the Siemens Teamcenter GTAC Support Site. Checking Database Integrity For all the sophisticated data management techniques embedded in the SQL Server database engine, there is still the possibility of some corruption occurring in a database, most notably as the result of a hardware glitch. To head off the potential impact of such problems, you should regularly check the integrity of the database. The statement for doing this in T-SQL is DBCC CHECKDB. It is best to include database integrity checks in a scheduled job that executes DBCC CHECKDB or through a scheduled Maintenance Plan that includes the Check Database Integrity task. If any problems are detected, you can restore from backups (usually the best option) or use one of the REPAIR options on DBCC CHECKDB. Changing the Recovery Model After verifying the health of your new SQL Server production database, you need to change the recovery model back to Full. Creating Database Backups It is recommended that you create full database backups, differential database backups, and transaction log backups in order to protect your database. You should use SSMS and create custom T-SQL backup scripts and SQL Server Agent jobs or use a Maintenance Plan to back up your database. You should also use a Maintenance Plan to back up your system databases on a weekly basis. Validating the Migration Through Teamcenter Use Cases The final step in your migration process is to test the use-case scenarios you determined at the start of your migration planning to verify your new production database. These scenarios should include the addition of new data and the validation of existing data between the Oracle database and the SQL Server database. Some common use cases affected by the migration process are customized form attributes in Teamcenter, as well as custom items, objects, and data types. Testing their functionality is of utmost importance. Further testing should be done on assemblies and viewer data to ensure correctness; however issues here should be rare or related to custom attributes. 64

Moving the TRITON Reporting Databases

Moving the TRITON Reporting Databases Moving the TRITON Reporting Databases Topic 50530 Web, Data, and Email Security Versions 7.7.x, 7.8.x Updated 06-Nov-2013 If you need to move your Microsoft SQL Server database to a new location (directory,

More information

HP Quality Center. Upgrade Preparation Guide

HP Quality Center. Upgrade Preparation Guide HP Quality Center Upgrade Preparation Guide Document Release Date: November 2008 Software Release Date: November 2008 Legal Notices Warranty The only warranties for HP products and services are set forth

More information

Moving the Web Security Log Database

Moving the Web Security Log Database Moving the Web Security Log Database Topic 50530 Web Security Solutions Version 7.7.x, 7.8.x Updated 22-Oct-2013 Version 7.8 introduces support for the Web Security Log Database on Microsoft SQL Server

More information

Update and Installation Guide for Microsoft Management Reporter 2.0 Feature Pack 1

Update and Installation Guide for Microsoft Management Reporter 2.0 Feature Pack 1 Update and Installation Guide for Microsoft Management Reporter 2.0 Feature Pack 1 Microsoft Corporation Published: December 2010 Microsoft Dynamics is a line of integrated, adaptable business management

More information

ecopy ShareScan 5.0 SQL installs guide

ecopy ShareScan 5.0 SQL installs guide ecopy ShareScan 5.0 SQL installs guide Created by Rob O Leary, 3/28/2011 5.0 SQL installs guide 2 ShareScan 5.0 has two SQL setup types: Complete: Installs and connects the local MS SQL Server 2008 Express

More information

Chancery SMS 7.5.0 Database Split

Chancery SMS 7.5.0 Database Split TECHNICAL BULLETIN Microsoft SQL Server replication... 1 Transactional replication... 2 Preparing to set up replication... 3 Setting up replication... 4 Quick Reference...11, 2009 Pearson Education, Inc.

More information

Making Database Backups in Microsoft Business Solutions Navision

Making Database Backups in Microsoft Business Solutions Navision Making Database Backups in Microsoft Business Solutions Navision MAKING DATABASE BACKUPS IN MICROSOFT BUSINESS SOLUTIONS NAVISION DISCLAIMER This material is for informational purposes only. Microsoft

More information

VMware vcenter Configuration Manager Backup and Disaster Recovery Guide vcenter Configuration Manager 5.7

VMware vcenter Configuration Manager Backup and Disaster Recovery Guide vcenter Configuration Manager 5.7 VMware vcenter Configuration Manager Backup and Disaster Recovery Guide vcenter Configuration Manager 5.7 This document supports the version of each product listed and supports all subsequent versions

More information

Database Maintenance Guide

Database Maintenance Guide Database Maintenance Guide Medtech Evolution - Document Version 5 Last Modified on: February 26th 2015 (February 2015) This documentation contains important information for all Medtech Evolution users

More information

Dynamics NAV/SQL Server Configuration Recommendations

Dynamics NAV/SQL Server Configuration Recommendations Dynamics NAV/SQL Server Configuration Recommendations This document describes SQL Server configuration recommendations that were gathered from field experience with Microsoft Dynamics NAV and SQL Server.

More information

Backing up and restoring HP Systems Insight Manager 6.0 or greater data files in a Windows environment

Backing up and restoring HP Systems Insight Manager 6.0 or greater data files in a Windows environment Technical white paper Backing up and restoring HP Systems Insight Manager 6.0 or greater data files in a Windows environment Table of contents Abstract 2 Introduction 2 Saving and restoring data files

More information

Project management integrated into Outlook

Project management integrated into Outlook Project management integrated into Outlook InLoox PM 7.x off-line operation An InLoox Whitepaper Published: October 2011 Copyright: 2011 InLoox GmbH. You can find up-to-date information at http://www.inloox.com

More information

SolarWinds Migrating SolarWinds NPM Technical Reference

SolarWinds Migrating SolarWinds NPM Technical Reference SolarWinds Migrating SolarWinds NPM Technical Reference Copyright 1995-2015 SolarWinds Worldwide, LLC. All rights reserved worldwide. No part of this document may be reproduced by any means nor modified,

More information

Migrating MSDE to Microsoft SQL 2008 R2 Express

Migrating MSDE to Microsoft SQL 2008 R2 Express How To Updated: 11/11/2011 2011 Shelby Systems, Inc. All Rights Reserved Other brand and product names are trademarks or registered trademarks of the respective holders. If you are still on MSDE 2000,

More information

SQL Server Integration Services with Oracle Database 10g

SQL Server Integration Services with Oracle Database 10g SQL Server Integration Services with Oracle Database 10g SQL Server Technical Article Published: May 2008 Applies To: SQL Server Summary: Microsoft SQL Server (both 32-bit and 64-bit) offers best-of breed

More information

Sophos Enterprise Console Auditing user guide. Product version: 5.2

Sophos Enterprise Console Auditing user guide. Product version: 5.2 Sophos Enterprise Console Auditing user guide Product version: 5.2 Document date: January 2013 Contents 1 About this guide...3 2 About Sophos Auditing...4 3 Key steps in using Sophos Auditing...5 4 Ensure

More information

SQL Server Maintenance Plans

SQL Server Maintenance Plans SQL Server Maintenance Plans BID2WIN Software, Inc. September 2010 Abstract This document contains information related to SQL Server 2005 and SQL Server 2008 and is a compilation of research from various

More information

http://support.microsoft.com/kb/878449 Notes Transfer instructions INTRODUCTION More information

http://support.microsoft.com/kb/878449 Notes Transfer instructions INTRODUCTION More information Page 1 of 6 How to transfer an existing Microsoft Dynamics GP, Microsoft Small Business Financials, or Microsoft Small Business Manager installation to a new server that is running Microsoft SQL Server

More information

Portions of this product were created using LEADTOOLS 1991-2009 LEAD Technologies, Inc. ALL RIGHTS RESERVED.

Portions of this product were created using LEADTOOLS 1991-2009 LEAD Technologies, Inc. ALL RIGHTS RESERVED. Installation Guide Lenel OnGuard 2009 Installation Guide, product version 6.3. This guide is item number DOC-110, revision 1.038, May 2009 Copyright 1992-2009 Lenel Systems International, Inc. Information

More information

EASRestoreService. Manual

EASRestoreService. Manual Manual Introduction EAS is a powerful Archiving Solution for Microsoft Exchange, Lotus Notes, Sharepoint and Windows based File systems. As one of the Top 5 Enterprise Archiving Solutions worldwide is

More information

Redeploying Microsoft CRM 3.0

Redeploying Microsoft CRM 3.0 Redeploying Microsoft CRM 3.0 2005 Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies,

More information

A Tutorial on SQL Server 2005. CMPT 354 Fall 2007

A Tutorial on SQL Server 2005. CMPT 354 Fall 2007 A Tutorial on SQL Server 2005 CMPT 354 Fall 2007 Road Map Create Database Objects Create a database Create a table Set a constraint Create a view Create a user Query Manage the Data Import data Export

More information

Copyright SolarWinds. All rights reserved worldwide. No part of this document may be reproduced by any means nor modified, decompiled,

Copyright SolarWinds. All rights reserved worldwide. No part of this document may be reproduced by any means nor modified, decompiled, APM Migration Introduction... 3 General Requirements... 3 Database Requirements... 3 Stopping APM Services... 4 Creating and Restoring Orion Database Backups... 4 Creating a Database Backup File with Database

More information

Performance. Optimizing Performance. Microsoft Dynamics CRM 3.0. White Paper. Date: January 10, 2007. http://go.microsoft.com/fwlink/?

Performance. Optimizing Performance. Microsoft Dynamics CRM 3.0. White Paper. Date: January 10, 2007. http://go.microsoft.com/fwlink/? Performance Microsoft Dynamics CRM 3.0 Optimizing Performance White Paper Date: January 10, 2007 http://go.microsoft.com/fwlink/?linkid=80916 Contents Summary... 5 Maintaining Databases and SQL Server...

More information

TIBCO Spotfire Server Migration. Migration Manual

TIBCO Spotfire Server Migration. Migration Manual TIBCO Spotfire Server Migration Migration Manual Revision date: 26 October 2012 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE

More information

Dell InTrust 11.0. Preparing for Auditing Microsoft SQL Server

Dell InTrust 11.0. Preparing for Auditing Microsoft SQL Server 2014 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement.

More information

VirtualCenter Database Maintenance VirtualCenter 2.0.x and Microsoft SQL Server

VirtualCenter Database Maintenance VirtualCenter 2.0.x and Microsoft SQL Server Technical Note VirtualCenter Database Maintenance VirtualCenter 2.0.x and Microsoft SQL Server This document discusses ways to maintain the VirtualCenter database for increased performance and manageability.

More information

Veritas Cluster Server Database Agent for Microsoft SQL Configuration Guide

Veritas Cluster Server Database Agent for Microsoft SQL Configuration Guide Veritas Cluster Server Database Agent for Microsoft SQL Configuration Guide Windows 2000, Windows Server 2003 5.0 11293743 Veritas Cluster Server Database Agent for Microsoft SQL Configuration Guide Copyright

More information

ImageNow for Microsoft SQL Server

ImageNow for Microsoft SQL Server ImageNow for Microsoft SQL Server Best Practices Guide ImageNow Version: 6.7. x Written by: Product Documentation, R&D Date: July 2013 2013 Perceptive Software. All rights reserved CaptureNow, ImageNow,

More information

www.novell.com/documentation Database Maintenance ZENworks Mobile Management 2.7.x August 2013

www.novell.com/documentation Database Maintenance ZENworks Mobile Management 2.7.x August 2013 www.novell.com/documentation Database Maintenance ZENworks Mobile Management 2.7.x August 2013 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of

More information

Creating IBM Cognos Controller Databases using Microsoft SQL Server

Creating IBM Cognos Controller Databases using Microsoft SQL Server Guideline Creating IBM Cognos Controller Databases using Microsoft SQL Product(s): IBM Cognos Controller 8.1 or higher Area of Interest: Financial Management 2 Copyright Copyright 2008 Cognos ULC (formerly

More information

Version 4.61 or Later. Copyright 2013 Interactive Financial Solutions, Inc. All Rights Reserved. ProviderPro Network Administration Guide.

Version 4.61 or Later. Copyright 2013 Interactive Financial Solutions, Inc. All Rights Reserved. ProviderPro Network Administration Guide. Version 4.61 or Later Copyright 2013 Interactive Financial Solutions, Inc. All Rights Reserved. ProviderPro Network Administration Guide. This manual, as well as the software described in it, is furnished

More information

Table of Contents SQL Server Option

Table of Contents SQL Server Option Table of Contents SQL Server Option STEP 1 Install BPMS 1 STEP 2a New Customers with SQL Server Database 2 STEP 2b Restore SQL DB Upsized by BPMS Support 6 STEP 2c - Run the "Check Dates" Utility 7 STEP

More information

Cascaded Lookup 5.0 User Guide

Cascaded Lookup 5.0 User Guide Cascaded Lookup 5.0 User Guide Copyright Copyright 2008-2013 BoostSolutions Co., Ltd. All rights reserved. All material contained in this publication is protected by Copyright and no part of this publication

More information

GO!NotifyLink. Database Maintenance. GO!NotifyLink Database Maintenance 1

GO!NotifyLink. Database Maintenance. GO!NotifyLink Database Maintenance 1 GO!NotifyLink Database Maintenance GO!NotifyLink Database Maintenance 1 Table of Contents Database Maintenance 3 Database Cleanup... 3 Database Backups... 3 Database Configuration... 4 The Procedure via

More information

Implementing Microsoft SQL Server 2008 Exercise Guide. Database by Design

Implementing Microsoft SQL Server 2008 Exercise Guide. Database by Design Implementing Microsoft SQL Server 2008 Exercise Guide Database by Design Installation Lab: This lab deals with installing the SQL Server 2008 database. The requirements are to have either a Windows 7 machine

More information

Version 1.2. 2011 Provance Technologies, Inc. All rights reserved. Provance Technologies Inc. 85 Bellehumeur Gatineau, Quebec CANADA J8T 8B7

Version 1.2. 2011 Provance Technologies, Inc. All rights reserved. Provance Technologies Inc. 85 Bellehumeur Gatineau, Quebec CANADA J8T 8B7 This document is provided for informational purposes only and Provance makes no warranties, either express or implied, in this document. Information in this document, including external references, is

More information

OFFICIAL MICROSOFT LEARNING PRODUCT 10775A. Lab Instructions and Lab Answer Key: Administering Microsoft SQL Server 2012 Database

OFFICIAL MICROSOFT LEARNING PRODUCT 10775A. Lab Instructions and Lab Answer Key: Administering Microsoft SQL Server 2012 Database OFFICIAL MICROSOFT LEARNING PRODUCT 10775A Lab Instructions and Lab Answer Key: Administering Microsoft SQL Server 2012 Database Information in this document, including URL and other Internet Web site

More information

Bosch ReadykeyPRO Unlimited Installation Guide, product version 6.5. This guide is item number DOC-110-2-029, revision 2.029, May 2012.

Bosch ReadykeyPRO Unlimited Installation Guide, product version 6.5. This guide is item number DOC-110-2-029, revision 2.029, May 2012. Bosch ReadykeyPRO Unlimited Installation Guide, product version 6.5. This guide is item number DOC-110-2-029, revision 2.029, May 2012. Copyright 1995-2012 Lenel Systems International, Inc. Information

More information

SharePoint Password Change & Expiration 3.0 User Guide

SharePoint Password Change & Expiration 3.0 User Guide SharePoint Password Change & Expiration 3.0 User Guide Copyright Copyright 2008-2013 BoostSolutions Co., Ltd. All rights reserved. All materials contained in this publication are protected by Copyright

More information

SPHOL207: Database Snapshots with SharePoint 2013

SPHOL207: Database Snapshots with SharePoint 2013 2013 SPHOL207: Database Snapshots with SharePoint 2013 Hands-On Lab Lab Manual This document is provided as-is. Information and views expressed in this document, including URL and other Internet Web site

More information

Integrate Microsoft Windows Hyper V

Integrate Microsoft Windows Hyper V Integrate Microsoft Windows Hyper V EventTracker v7.x Publication Date: Aug 9, 2014 EventTracker 8815 Centre Park Drive Columbia MD 21045 www.eventtracker.com Abstract Hyper-V in Windows Server 2008 and

More information

SQL Server Database Administrator s Guide

SQL Server Database Administrator s Guide SQL Server Database Administrator s Guide Copyright 2011 Sophos Limited. All rights reserved. No part of this publication may be reproduced, stored in retrieval system, or transmitted, in any form or by

More information

vcenter Configuration Manager Backup and Disaster Recovery Guide VCM 5.3

vcenter Configuration Manager Backup and Disaster Recovery Guide VCM 5.3 vcenter Configuration Manager Backup and Disaster Recovery Guide VCM 5.3 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by

More information

Using SQL Reporting Services with Amicus

Using SQL Reporting Services with Amicus Using SQL Reporting Services with Amicus Applies to: Amicus Attorney Premium Edition 2011 SP1 Amicus Premium Billing 2011 Contents About SQL Server Reporting Services...2 What you need 2 Setting up SQL

More information

StruxureWare Power Monitoring 7.0.1. Database Upgrade FAQ

StruxureWare Power Monitoring 7.0.1. Database Upgrade FAQ StruxureWare Power Monitoring 7.0.1 Database Upgrade FAQ Document Overview Author Power Software, Schneider Electric Last Revised 10 th July 2012 Document Purpose Upgrading ION-Enterprise to StruxureWare

More information

Upgrading a Microsoft Dynamics NAV 2009 R2 or Microsoft Dynamics NAV 2009 SP1 Database to Microsoft Dynamics NAV 2015

Upgrading a Microsoft Dynamics NAV 2009 R2 or Microsoft Dynamics NAV 2009 SP1 Database to Microsoft Dynamics NAV 2015 Upgrading a Microsoft Dynamics NAV 2009 R2 or Microsoft Dynamics NAV 2009 SP1 Database to Microsoft Dynamics NAV 2015 White Paper November 2014 Contents Introduction... 3 Data Upgrade Short Overview...

More information

ODBC Client Driver Help. 2015 Kepware, Inc.

ODBC Client Driver Help. 2015 Kepware, Inc. 2015 Kepware, Inc. 2 Table of Contents Table of Contents 2 4 Overview 4 External Dependencies 4 Driver Setup 5 Data Source Settings 5 Data Source Setup 6 Data Source Access Methods 13 Fixed Table 14 Table

More information

SQL 2014 Configuration Guide

SQL 2014 Configuration Guide SQL 2014 Configuration Guide 2015 ImproMed, LLC. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language

More information

Dell Statistica 13.0. Statistica Enterprise Installation Instructions

Dell Statistica 13.0. Statistica Enterprise Installation Instructions Dell Statistica 13.0 2015 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or

More information

SQL Server An Overview

SQL Server An Overview SQL Server An Overview SQL Server Microsoft SQL Server is designed to work effectively in a number of environments: As a two-tier or multi-tier client/server database system As a desktop database system

More information

Portions of this product were created using LEADTOOLS 1991-2010 LEAD Technologies, Inc. ALL RIGHTS RESERVED.

Portions of this product were created using LEADTOOLS 1991-2010 LEAD Technologies, Inc. ALL RIGHTS RESERVED. Installation Guide Lenel OnGuard 2010 Installation Guide, product version 6.4. This guide is item number DOC-110, revision 1.045, May 2010 Copyright 1995-2010 Lenel Systems International, Inc. Information

More information

Microsoft Dynamics NAV 2013 R2 Release Notes Follow-up

Microsoft Dynamics NAV 2013 R2 Release Notes Follow-up Microsoft Dynamics NAV 2013 R2 Release Notes Follow-up October 2012 Contents Introduction 3 By Design Issues 3 Windows PowerShell 3.0 required before installing Microsoft Dynamics NAV 2013 R2 3 Extensive

More information

Moving a Romexis Database to an Existing SQL Instance

Moving a Romexis Database to an Existing SQL Instance Moving a Romexis Database to an Existing SQL Instance Microsoft Excerpt: 2.10 Installing SQL Server Express on a Windows Domain Controller Security Note We (Microsoft) recommend against running SQL Server

More information

Lab 02 Working with Data Quality Services in SQL Server 2014

Lab 02 Working with Data Quality Services in SQL Server 2014 SQL Server 2014 BI Lab 02 Working with Data Quality Services in SQL Server 2014 Jump to the Lab Overview Terms of Use 2014 Microsoft Corporation. All rights reserved. Information in this document, including

More information

Installation Manual Version 8.5 (w/sql Server 2005)

Installation Manual Version 8.5 (w/sql Server 2005) C ase Manag e m e n t by C l i e n t P rofiles Installation Manual Version 8.5 (w/sql Server 2005) T E C H N O L O G Y F O R T H E B U S I N E S S O F L A W Table of Contents - 2 - Table of Contents SERVER

More information

Item Audit Log 2.0 User Guide

Item Audit Log 2.0 User Guide Item Audit Log 2.0 User Guide Item Audit Log 2.0 User Guide Page 1 Copyright Copyright 2008-2013 BoostSolutions Co., Ltd. All rights reserved. All materials contained in this publication are protected

More information

VMware vcenter Configuration Manager Backup and Disaster Recovery Guide vcenter Configuration Manager 5.4.1

VMware vcenter Configuration Manager Backup and Disaster Recovery Guide vcenter Configuration Manager 5.4.1 VMware vcenter Configuration Manager Backup and Disaster Recovery Guide vcenter Configuration Manager 5.4.1 This document supports the version of each product listed and supports all subsequent versions

More information

Migration from Oracle Database to SQL Server 2012 FAQ

Migration from Oracle Database to SQL Server 2012 FAQ Migration from Oracle Database to SQL Server 2012 FAQ SQL Server FAQ Article Published: August 2012 Applies to: SQL Server 2012 Summary: Review this FAQ to find answers to common questions about using

More information

If you have questions or need assistance, contact PCS Technical Services using the contact information on page 10.

If you have questions or need assistance, contact PCS Technical Services using the contact information on page 10. PCS Axis Database Backup and Restore Best Practices October 2014 Introduction This document explains how to backup and restore a PCS Axis database using Microsoft SQL Server Management Studio (SSMS). The

More information

LANDesk Management Suite 8. Microsoft* SQL Server* 2000 Configuration

LANDesk Management Suite 8. Microsoft* SQL Server* 2000 Configuration LANDesk Management Suite 8 Microsoft* SQL Server* 2000 Configuration November 19, 2003 Copyright 2003, LANDesk Software, Ltd. All rights reserved. Information in this document is provided in connection

More information

Windows Small Business Server 2003 Upgrade Best Practices

Windows Small Business Server 2003 Upgrade Best Practices Windows Small Business Server 2003 Upgrade Best Practices Microsoft Corporation Published: May 2005 Version: 1 Abstract To ensure a successful upgrade from the Microsoft Windows Small Business Server 2003

More information

Automated Database Backup. Procedure to create an automated database backup using SQL management tools

Automated Database Backup. Procedure to create an automated database backup using SQL management tools Automated Database Backup Procedure to create an automated database backup using SQL management tools Genetec Technical Support 6/29/2009 Notice This manual, and the software that it describes, is provided

More information

Video Administration Backup and Restore Procedures

Video Administration Backup and Restore Procedures CHAPTER 12 Video Administration Backup and Restore Procedures This chapter provides procedures for backing up and restoring the Video Administration database and configuration files. See the following

More information

SELF SERVICE RESET PASSWORD MANAGEMENT BACKUP GUIDE

SELF SERVICE RESET PASSWORD MANAGEMENT BACKUP GUIDE SELF SERVICE RESET PASSWORD MANAGEMENT BACKUP GUIDE Copyright 1998-2015 Tools4ever B.V. All rights reserved. No part of the contents of this user guide may be reproduced or transmitted in any form or by

More information

mylittleadmin for MS SQL Server Quick Start Guide

mylittleadmin for MS SQL Server Quick Start Guide mylittleadmin for MS SQL Server Quick Start Guide version 3.5 1/25 CONTENT 1 OVERVIEW... 3 2 WHAT YOU WILL LEARN... 3 3 INSTALLATION AND CONFIGURATION... 3 4 BASIC NAVIGATION... 4 4.1. Connection 4 4.2.

More information

DBMoto 6.5 Setup Guide for SQL Server Transactional Replications

DBMoto 6.5 Setup Guide for SQL Server Transactional Replications DBMoto 6.5 Setup Guide for SQL Server Transactional Replications Copyright This document is copyrighted and protected by worldwide copyright laws and treaty provisions. No portion of this documentation

More information

HELP DOCUMENTATION E-SSOM BACKUP AND RESTORE GUIDE

HELP DOCUMENTATION E-SSOM BACKUP AND RESTORE GUIDE HELP DOCUMENTATION E-SSOM BACKUP AND RESTORE GUIDE Copyright 1998-2012, Tools4ever B.V. All rights reserved. No part of the contents of this user guide may be reproduced or transmitted in any form or by

More information

CA ARCserve Backup for Windows

CA ARCserve Backup for Windows CA ARCserve Backup for Windows Agent for Microsoft SharePoint Server Guide r15 This documentation and any related computer software help programs (hereinafter referred to as the "Documentation") are for

More information

Microsoft Dynamics GP. Engineering Data Management Integration Administrator s Guide

Microsoft Dynamics GP. Engineering Data Management Integration Administrator s Guide Microsoft Dynamics GP Engineering Data Management Integration Administrator s Guide Copyright Copyright 2007 Microsoft Corporation. All rights reserved. Complying with all applicable copyright laws is

More information

Using InstallAware 7. To Patch Software Products. August 2007

Using InstallAware 7. To Patch Software Products. August 2007 Using InstallAware 7 To Patch Software Products August 2007 The information contained in this document represents the current view of InstallAware Software Corporation on the issues discussed as of the

More information

StarterPak: HubSpot and Dynamics CRM Lead and Contact Synchronization

StarterPak: HubSpot and Dynamics CRM Lead and Contact Synchronization StarterPak: HubSpot and Dynamics CRM Lead and Contact Synchronization Version 1.1 2/10/2015 Important Notice No part of this publication may be reproduced, stored in a retrieval system, or transmitted

More information

SQL Tips and Tricks for Dynamics GP. Lisa Williams and Darrell Moy

SQL Tips and Tricks for Dynamics GP. Lisa Williams and Darrell Moy for Dynamics GP Lisa Williams and Darrell Moy Agenda 1. SQL Database Maintenance Plans 2. SQL Jobs Check job status 3. Creating a view for custom SmartList & Reporting 4. Create SQL script using Mail Merge

More information

IMPORTANT: The person who installs and sets up the PCS Axis database on the central database server

IMPORTANT: The person who installs and sets up the PCS Axis database on the central database server PCS Axis v1.9 Client/Server New Installation (without Replication) May 2015 Introduction American Innovations (AI) is pleased to announce version 1.9 of our Pipeline Compliance System Axis software (PCS

More information

Sophos Enterprise Console server to server migration guide. Product version: 5.2

Sophos Enterprise Console server to server migration guide. Product version: 5.2 Sophos Enterprise Console server to server migration guide Product : 5.2 Document date: December 2014 Contents 1 About this guide...3 2 Terminology...4 3 Assumptions...5 4 Prerequisite...6 5 What are the

More information

Reconfiguration of VMware vcenter Update Manager

Reconfiguration of VMware vcenter Update Manager Reconfiguration of VMware vcenter Update Manager Update 1 vcenter Update Manager 4.1 This document supports the version of each product listed and supports all subsequent versions until the document is

More information

Server Installation Guide ZENworks Patch Management 6.4 SP2

Server Installation Guide ZENworks Patch Management 6.4 SP2 Server Installation Guide ZENworks Patch Management 6.4 SP2 02_016N 6.4SP2 Server Installation Guide - 2 - Notices Version Information ZENworks Patch Management Server Installation Guide - ZENworks Patch

More information

Database Migration and Management Guide v15.0

Database Migration and Management Guide v15.0 Database Migration and Management Guide v15.0 Learn how to migrate a WhatsUp Gold database from Microsoft SQL Server 2005 Express Edition to Microsoft SQL Server 2005 or 2008 Enterprise, Standard, or Workgroup

More information

Arcserve Backup for Windows

Arcserve Backup for Windows Arcserve Backup for Windows Agent for Microsoft SharePoint Server Guide r16 Pre-release Document, only for reference This Documentation, which includes embedded help systems and electronically distributed

More information

All rights reserved. Trademarks

All rights reserved. Trademarks All rights reserved This manual, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. The content of this manual

More information

Copyrights, Legal Notices, Trademarks and Servicemarks

Copyrights, Legal Notices, Trademarks and Servicemarks Installation Guide Copyrights, Legal Notices, Trademarks and Servicemarks Copyright 1998-2003 Westbrook Technologies Incorporated. All rights reserved. No part of this work may be reproduced or transmitted

More information

Copying data from SQL Server database to an Oracle Schema. White Paper

Copying data from SQL Server database to an Oracle Schema. White Paper Copying data from SQL Server database to an Oracle Schema White Paper Copyright Decipher Information Systems, 2005. All rights reserved. The information in this publication is furnished for information

More information

WhatsUp Gold v16.0 Database Migration and Management Guide Learn how to migrate a WhatsUp Gold database from Microsoft SQL Server 2005 Express

WhatsUp Gold v16.0 Database Migration and Management Guide Learn how to migrate a WhatsUp Gold database from Microsoft SQL Server 2005 Express WhatsUp Gold v16.0 Database Migration and Management Guide Learn how to migrate a WhatsUp Gold database from Microsoft SQL Server 2005 Express Edition or SQL Server 2008 Express R2 to Microsoft SQL Server

More information

How to Set Up a Shared SQL Express Database with ManagePro 7 Standard version

How to Set Up a Shared SQL Express Database with ManagePro 7 Standard version How to Set Up a Shared SQL Express Database with ManagePro 7 Standard version This instruction set is provided AS IS without warranty, express or implied, including but not limited to the implied warranties

More information

Microsoft Corporation. Project Server 2010 Installation Guide

Microsoft Corporation. Project Server 2010 Installation Guide Microsoft Corporation Project Server 2010 Installation Guide Office Asia Team 11/4/2010 Table of Contents 1. Prepare the Server... 2 1.1 Install KB979917 on Windows Server... 2 1.2 Creating users and groups

More information

Veeam Backup Enterprise Manager. Version 7.0

Veeam Backup Enterprise Manager. Version 7.0 Veeam Backup Enterprise Manager Version 7.0 User Guide August, 2013 2013 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication may

More information

WHITE PAPER: ENTERPRISE SOLUTIONS. Symantec Backup Exec Continuous Protection Server Continuous Protection for Microsoft SQL Server Databases

WHITE PAPER: ENTERPRISE SOLUTIONS. Symantec Backup Exec Continuous Protection Server Continuous Protection for Microsoft SQL Server Databases WHITE PAPER: ENTERPRISE SOLUTIONS Symantec Backup Exec Continuous Protection Server Continuous Protection for Microsoft SQL Server Databases White Paper: Enterprise Solutions Symantec Backup Exec Continuous

More information

Mobility Services Platform 3.1.1 Software Installation Guide

Mobility Services Platform 3.1.1 Software Installation Guide Mobility Services Platform 3.1.1 Software Installation Guide Mobility Services Platform 3.1.1 Software Installation Guide 72E-100159-04 Revision D January 2008 2007 by Motorola, Inc. All rights reserved.

More information

XMailer Reference Guide

XMailer Reference Guide XMailer Reference Guide Version 7.00 Wizcon Systems SAS Information in this document is subject to change without notice. SyTech assumes no responsibility for any errors or omissions that may be in this

More information

Xcalibur Global Version 1.2 Installation Guide Document Version 3.0

Xcalibur Global Version 1.2 Installation Guide Document Version 3.0 Xcalibur Global Version 1.2 Installation Guide Document Version 3.0 December 2010 COPYRIGHT NOTICE TRADEMARKS 2010 Chip PC Inc., Chip PC (Israel) Ltd., Chip PC (UK) Ltd., Chip PC GmbH All rights reserved.

More information

Sophos Enterprise Console server to server migration guide. Product version: 5.1 Document date: June 2012

Sophos Enterprise Console server to server migration guide. Product version: 5.1 Document date: June 2012 Sophos Enterprise Console server to server migration guide Product : 5.1 Document date: June 2012 Contents 1 About this guide...3 2 Terminology...4 3 Assumptions...5 4 Prerequisite...6 5 What are the key

More information

SafeGuard Enterprise upgrade guide. Product version: 6.1

SafeGuard Enterprise upgrade guide. Product version: 6.1 SafeGuard Enterprise upgrade guide Product version: 6.1 Document date: February 2014 Contents 1 About this guide...3 2 Check the system requirements...4 3 Download installers...5 4 About upgrading...6

More information

HELP DOCUMENTATION E-SSOM BACKUP AND RESTORE GUIDE

HELP DOCUMENTATION E-SSOM BACKUP AND RESTORE GUIDE HELP DOCUMENTATION E-SSOM BACKUP AND RESTORE GUIDE Copyright 1998-2013 Tools4ever B.V. All rights reserved. No part of the contents of this user guide may be reproduced or transmitted in any form or by

More information

Database Administration Guide

Database Administration Guide Database Administration Guide 013008 2008 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any means, electronic, or mechanical, including photocopying,

More information

SQL Server Replication Guide

SQL Server Replication Guide SQL Server Replication Guide Rev: 2013-08-08 Sitecore CMS 6.3 and Later SQL Server Replication Guide Table of Contents Chapter 1 SQL Server Replication Guide... 3 1.1 SQL Server Replication Overview...

More information

Migrating to Azure SQL Database

Migrating to Azure SQL Database Migrating to Azure SQL Database Contents Azure account required for lab... 3 SQL Azure Migration Wizard Overview... 3 Provisioning an Azure SQL Database... 4 Exercise 1: Analyze and resolve... 8 Exercise

More information

GFI MailArchiver for Exchange 4. Manual. By GFI Software

GFI MailArchiver for Exchange 4. Manual. By GFI Software GFI MailArchiver for Exchange 4 Manual By GFI Software http://www.gfi.com Email: info@gfi.com Information in this document is subject to change without notice. Companies, names, and data used in examples

More information

ICE for Eclipse. Release 9.0.1

ICE for Eclipse. Release 9.0.1 ICE for Eclipse Release 9.0.1 Disclaimer This document is for informational purposes only and is subject to change without notice. This document and its contents, including the viewpoints, dates and functional

More information

Exclaimer Mail Archiver

Exclaimer Mail Archiver Deployment Guide - Outlook Add-In www.exclaimer.com Contents About This Guide... 3 System Requirements... 4 Software... 4 Installation Files... 5 Deployment Preparation... 6 Installing the Add-In Manually...

More information

WhatsUp Gold v16.2 Database Migration and Management Guide

WhatsUp Gold v16.2 Database Migration and Management Guide WhatsUp Gold v16.2 Database Migration and Management Guide Contents CHAPTER 1 How to use this guide CHAPTER 2 Migrating the WhatsUp Gold Microsoft SQL Server 2008 R2 Express Edition database to Microsoft

More information