We've been talking quite a bit about database & application migrations, as well as interoperability with exiting infrastructure, applications and reporting tools with SQL Server. I suppose I should also mention that this blog contains a bit of information about Microsoft business intelligence using SQL Server as the database or just parts of the SQL Server system such as Analysis Services, Integration Services or Reporting Services.
Well, simply put, there is a lot there. A lot to consume and a lot to think about. But it would be somewhat incomplete to not talk about operating system migrations. So I'll spend today's post with a little bit of information and include public Microsoft links to further information regarding operating system migrations and interopability and how that all relates to database migrations and consolidations in the context of DBCF, database consolidation framework.
Let's say that you have an Oracle 9i database that is hosting a couple of internally-developed Java applications in your organization. The Oracle database is currently hosted on Sun Solaris, let's say, and you are looking to migrating these applications as-is to SQL Server 2005.
Well, the DBCF guidebook for migrations would point you toward SSMA for Oracle for the existing database schema and existing data migration from Oracle 9i to SQL Server 2005. Then you would need the SQL Server JDBC driver to replace the Oracle JDBC driver for database connectivity. The next step would be to evaluate the JDBC calls used by the developers to ensure that they are not using any Oracle-specific non-standard JDBC calls, which would require rewriting those lines of code if that is the case.
But for the operating system you may have scripts, jobs, etc. that you would like to port in-place over to Windows. The options you have include using server virtualization to host Solaris environments on your Windows 2003 servers, port to Windows scripting host, and in fact, you could even host Oracle in Windows 2003 Server natively, or through virtualization within Windows Server.
Here is the primary Windows migration link to start with when migration from Unix systems: http://www.microsoft.com/windowsserver/unix/default.mspx
For mainframe migrations, which you will find often when migrating to SQL Server from IBM DB2, start here: http://www.microsoft.com/windowsserver/mainframe/migration.mspx
Lastly, I mentioned Windows Scripting earlier. There is quite a bit that you can do in Windows through scripting similar to that of Unix shell scripting, if that is what you are comfortable doing as an administrator. Aside from porting Perl to Windows-based ActivePerl, have a look here at a great TechNet site on scripting:http://www.microsoft.com/technet/scriptcenter/default.mspx
Happy migrating! Mark (DBCF)