SQL Procedure Language (SQL PL) is used in DB2 to write database-stored procedures. Stored procedures are used to encapsulate business logic on the database and yield the following benefits: significantly improved application performance, increased application scalability, simplified application development, and reduced network traffic. This book will teach the reader how to set up the development environment and use all language elements of SQL PL through concrete examples and thorough discussions. Also included are expert tips and best practices for achieving optimal performance and code manageability. This book will be a valuable reference for SQL PL code syntax and troubleshooting. There are currently no books on the market that cover the DB2 SQL Procedure Language, although it is extensively used by IBM business partners and other software vendors.
Customer Reviews:
Avg. Customer Rating: 5.0 / 5.0
iF YOU WANT TO GO DEEPER IN SPL:
It is really a very good book from IBM about DB2-SPL. In our company we bougth a lot of DB2 book, but this is the very best. from basics to tricks
DB2(R) SQL PL: Essential Guide for DB2(R) UDB on Linux(TM), UNIX(R), Windows(TM), i5/OS(TM), and z/OS(R) (2nd Edition:
Has been extremely helpful. Good information
A very good book on DB2 SQL PL:
I didn't know anything about writing DB2 stored procedures until I bought this book. After reading it I have written several procedures to aid in data migration. It is well laid out and has all the necessary information. The best part is that you don't feel like you are reading a technical book.
embed yourself in db2:
The book describes IBM's Procedural Language, which runs on their db2 servers. It is not a general purpose language, like C or Java. Rather, it is tied directly to db2 and IBM's implementation of SQL. But within this context, the book explains the expressive power of PL. It shows at length how you can write stored procedures, triggers and functions in PL. The level of detail and the cited examples should reassure you of PL's capability. But why even write business logic code at the database layer?... more info
