Skip to main content

An Introduction to PL/SQL

Just getting started with PL/SQL? You will find PL/SQL to be a very readable and accessible programming language. You'll be productive in a very short amount of time!

I offer this post as a quick way to access a number of resources that will provide a nicely-paced introduction to this powerful database programming language. Of course, it helps a lot to know SQL, too, so check out the Other Useful Links at the bottom of the post.

I wrote a series of "PL/SQL 101" articles for Oracle Magazine several years ago. Here's a convenient index to all those articles:

1. Building with Blocks - an overview of PL/SQL, followed by coverage of some fundamentals
2. Controlling the Flow of Execution - conditional statements and loops
3. Working with Strings
4. Working with Numbers
5. Working with Dates
6. Error Management
7. Working with Records
8. Working with Collections
9. Bulk Processing with BULK COLLECT and FORALL
10. The Data Dictionary: Make Views Work for You
11. Wrap Your Code in a Neat Package
12. Working with Cursors

I added several "PL/SQL 101" posts on this blog as well:

Nulls in PL/SQL
Declaring variables and constants
Writing conditional logic in PL/SQL

Other Useful Links

Oracle PL/SQL home page - latest news, links to lots of other resources

Oracle SQL home page - 'cause what's PL/SQL without SQL?

Database for Developers: Fundamentals - an Oracle Dev Gym class that introduces to fundamental relational database concepts

Database for Developers: Next Level - an Oracle Dev Gym class that makes sure you have a solid foundation in basic SQL operations

Introduction to PL/SQL - FREE online class from the Oracle Learning Library

PL/SQL Tutorial from DatabaseStar - a free seven-part tutorial on basic PL/SQL concepts, packed with easy to follow examples.

Labels:

Comments

Post a Comment

Popular posts from this blog

Quick Guide to User-Defined Types in Oracle PL/SQL

A Twitter follower recently asked for more information on user-defined types in the PL/SQL language, and I figured the best way to answer is to offer up this blog post. PL/SQL is a strongly-typed language . Before you can work with a variable or constant, it must be declared with a type (yes, PL/SQL also supports lots of implicit conversions from one type to another, but still, everything must be declared with a type). PL/SQL offers a wide array of pre-defined data types , both in the language natively (such as VARCHAR2, PLS_INTEGER, BOOLEAN, etc.) and in a variety of supplied packages (e.g., the NUMBER_TABLE collection type in the DBMS_SQL package). Data types in PL/SQL can be scalars, such as strings and numbers, or composite (consisting of one or more scalars), such as record types, collection types and object types. You can't really declare your own "user-defined" scalars, though you can define subtypes  from those scalars, which can be very helpful from the p
24 comments
Read more

The differences between deterministic and result cache features

 EVERY once in a while, a developer gets in touch with a question like this: I am confused about the exact difference between deterministic and result_cache. Do they have different application use cases? I have used deterministic feature in many functions which retrieve data from some lookup tables. Is it essential to replace these 'deterministic' key words with 'result_cache'?  So I thought I'd write a post about the differences between these two features. But first, let's make sure we all understand what it means for a function to be  deterministic. From Wikipedia : In computer science, a deterministic algorithm is an algorithm which, given a particular input, will always produce the same output, with the underlying machine always passing through the same sequence of states.  Another way of putting this is that a deterministic subprogram (procedure or function) has no side-effects. If you pass a certain set of arguments for the parameters, you will always get
14 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch,
4 comments
Read more