<div>
<a href="http://www.google.co.il/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=1&ved=0CDkQFjAA&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2FC%2F0%2FC%2FC0C8C15A-32AD-418E-85BF-A6FF0CCE052C%2FMigrateDB2toSQLServer_2009.pdf&ei=kwl0T77ZNIiUOrTYmEw&usg=AFQjCNGGrLBKAcpArRMgmNG0UFgTg2pYpA" rel="ugc">http://www.google.co.il/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=1&ved=0CDkQFjAA&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2FC%2F0%2FC%2FC0C8C15A-32AD-418E-85BF-A6FF0CCE052C%2FMigrateDB2toSQLServer_2009.pdf&ei=kwl0T77ZNIiUOrTYmEw&usg=AFQjCNGGrLBKAcpArRMgmNG0UFgTg2pYpA</a><br />
<br />
<a href="http://www.microsoft.com/sqlserver/en/us/product-info/migration.aspx" rel="ugc">http://www.microsoft.com/sqlserver/en/us/product-info/migration.aspx</a><br />
<br />
what do you need to migrate?<br />
only objects and data? or do you have stored procedures and user functions in your db2 as well?
</div>


http://www.google.co.il/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=1&ved=0CDkQFjAA&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2FC%2F0%2FC%2FC0C8C15A-32AD-418E-85BF-A6FF0CCE052C%2FMigrateDB2toSQLServer_2009.pdf&ei=kwl0T77ZNIiUOrTYmEw&usg=AFQjCNGGrLBKAcpArRMgmNG0UFgTg2pYpA [http://www.google.co.il/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=1&ved=0CDkQFjAA&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2FC%2F0%2FC%2FC0C8C15A-32AD-418E-85BF-A6FF0CCE052C%2FMigrateDB2toSQLServer_2009.pdf&ei=kwl0T77ZNIiUOrTYmEw&usg=AFQjCNGGrLBKAcpArRMgmNG0UFgTg2pYpA]

http://www.microsoft.com/sqlserver/en/us/product-info/migration.aspx [http://www.microsoft.com/sqlserver/en/us/product-info/migration.aspx]

what do you need to migrate?
only objects and data? or do you have stored procedures and user functions in your db2 as well?

<div>
<div class="content wysiwyg-content">
I have a project coming up to migrate an client from JD Edwards Oneworld running on iSeries to SQL Server Windows plateform.<br />
<br />
I have only performed this task once and that was about 10 years ago. <br />
<br />
So I wanted to try and contact some iSeries experts (like Gary) who have iSeries experience and also JD Edwards and any high-level steps for migrating off iSeries onto Windows. Or any documentation you could provide would be even better.<br />
<br />
Once I migrate them onto Windows/SQL Server i will need to perform an upgrade from OneWorld to EnterpriseOne 9.0.<br />
<br />
Thanks<br />
John
</div>
</div>


I have a project coming up to migrate an client from JD Edwards Oneworld running on iSeries to SQL Server Windows plateform.

I have only performed this task once and that was about 10 years ago. 

So I wanted to try and contact some iSeries experts (like Gary) who have iSeries experience and also JD Edwards and any high-level steps for migrating off iSeries onto Windows. Or any documentation you could provide would be even better.

Once I migrate them onto Windows/SQL Server i will need to perform an upgrade from OneWorld to EnterpriseOne 9.0.

Thanks
John

How To Migrate Databases From iSeries to SQL Server (Windows)?

IBM DB2 is a family of relational database server products developed by IBM that have been extended to support object-relational features and non-relational structures like JSON and XML. There are three main products in the DB2 family: DB2 for Linux, UNIX and Windows (informally known as DB2 LUW), DB2 for z/OS (mainframe), and DB2 for i (formerly OS/400), plus a version for IBM's Virtual Storage Extended (VSE) operating system.

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

A mainframe operating system is networking software infrastructure that allows a mainframe computer to run programs, connect linked machines, and process complex numerical and data-driven tasks. Modern mainframe design is generally defined by redundant internal engineering, extensive input-output facilities, strict backward compatibility with older software, high hardware and computational utilization rates and high stability and reliability. Well-known operating systems include IBM z/OS, z/VM, zTPF, z/VSE, OS/390, and their predecessors, along with MCP for Unisys ClearPath, and NonStop OS/Guardian on HP/Tandem, and questions regarding the IBM midrange operating system called IBM i, OS/400, and i5/OS.