Solution Guide for Migrating Oracle on UNIX to SQL Server - Willy .Net

<strong>Solution</strong> <strong>Guide</strong> <strong>for</strong> <strong>Migrating</strong> <strong>Oracle</strong> on UNIX to SQL Server on Windows 19●●Relevant. The vision statement should relate to the business problem beingaddressed. If not, the project team might realize that they are solving the wrongproblem, or one that does not exist, and — in the process — lose sponsorship.Time-based. The vision statement should clearly indicate the estimated time frame<strong>for</strong> the delivery of the solution.The following two examples are vision statements <strong>for</strong> an <strong>Oracle</strong> on UNIX to SQL Serveron Windows migration project:● Be<strong>for</strong>e the end of the year, our customer support staff will be able to retrieve allcustomer data and account history within three seconds of the customer identifyinghimself or herself.● Be<strong>for</strong>e the start of the next fiscal year, our product managers will have access todaily sales reports from all the showrooms in the country.Define the User ProfilesUnderstanding the users <strong>for</strong> whom the solution is being developed is critical to theproject's success. To capture a clear description of each user, the team creates profilesof each user class. The process of profiling develops a set of user requirements. Thecombination of these user requirements with the business and design requirements willhelp to define the project scope later in the Envisioning Phase.In an <strong>Oracle</strong> on UNIX to SQL Server on Windows migration project, the most importantprofiles are that of the system managers and users of the migrated application. Considerthe following while profiling the user types:● Proficiency of the users in using Microsoft applications and the Windowsenvironment. Administrators largely use command line tools in the <strong>Oracle</strong>/UNIXworld. While Windows also provides some command line interfaces, Windowstools tend to be graphical user interfaces (GUIs). Users new to the Windowsenvironment may need training.● The type of tasks that the users will per<strong>for</strong>m on the new system.● Essential expectations of the end user from the current application interface thatwill have to be met in the new environment.● The language localization needs <strong>for</strong> the end users, if necessary. Consider the GUIas well as user documentation.● The physical location of the end users. Factors such as locations, number of usersat each location, and the bandwidth and usage of network links between the sitesshould be understood and documented.Assess the Current Situation (High Level)Organizations planning an <strong>Oracle</strong> on UNIX to SQL Server on Windows migration need toconsider the following five entities <strong>for</strong> a successful migration. While these entities areassessed in detail in the Planning Phase of the project, a high level preliminaryassessment is essential in the Envisioning Phase to evaluate the feasibility of the project.● ApplicationThis entity includes the target applications that are migration candidates. Whileassessing applications, the following questions should be asked:● Which are the specific applications that are to be migrated?● What languages are these applications written in?