porting sql stored procedures between db2 and sql server

[Steve Richter]

Would appreciate some help settling a friendly argument

What is the degree of difficulty of porting an sql procedure from a db2
database application to a sql server database application?

The following statement, is it accurate:

"...DB2 UDB for iSeries, and the broader DB2 UDB Family's support of
SQL Stored Procedures, is based on the SQL Persistent Stored Modules
(PSM) industry standard. Microsoft SQL Server stored procedures are
based on a proprietary language known as Transact SQL. Porting SQL
Procedures across the DB2 Family is easily accomplished because of the
common support for the PSM standard. Porting a DB2 SQL procedure to
Microsoft SQL Server requires manual conversion by the programmer due
to Microsoft's proprietary procedural language. IBM has provided the
DB2 Migration Toolkit to automate the conversion of proprietary
Transact SQL procedures to the standard SQL syntax that the DB2 Family
supports. ..."

If SQLServer does not adhere to the "SQL Persistent Stored Modules"
industry standard, are there software migration tools available which
translate db2 sql code to sql server sql?

thanks,

-Steve

 

[Steve Richter]

found this:

http://www.swissql.com/products/db2-to-sqlserver/db2-to-sql-server.html

curious to know about sql standards and whether SQL Server adheres to
them or not.

-Steve

 

[William \(Bill\) Vaughn]

Generally, all of the major vendors "support" basic ANSI SQL constructs, but
most developers don't stick to those standards. It's like building a car
that complies with federal regulations won't attract many buyers. It's those
cars that exceed the specs and have lots of interesting features that
improve sales.
TSQL is no exception. It's ANSI compliant but it supports a number of
powerful features above and beyond the spec. I expect DB2 is the same. If
their SQL is simple, it should move over easily. However, your applications
are usually written with the characteristics and behaviors, side-effects and
issues built-in. This makes the applications more efficient and in some
cases just work. It's those adaptations to DB2's way of doing things, the
way it implements special features or what issues you have to code around
that makes it tough to migrate.

--
William (Bill) Vaughn
President and Founder Beta V Corporation
Redmond, WA
(425) 556-9205
Microsoft MVP, Author, Mentor
Microsoft MVP