|
by Steven Feuerstein
Which of the following does not help you execute multiple PL/SQL programs simultaneously? This is the puzzler question that stumped a lot of our readers. In this article, Steven goes over the correct answer and provides some additional explanation. >Read full article
by Bonnie Baker
In the third part of this series, we'll look at how DSNZPARMs are used to control the maximum number of locks we may acquire, the length of time we'll wait for a lock, and other system-level issues. We will also explore timeouts, lock escalation vs. lock upgrades, and deadlocks. We'll also find out how an index-only job can time out even though we don't get locks on indexes. >Read full article
by Guy Harrison
MySQL 5 introduced stored procedures, allowing us to write programs that are stored in and executed in the database server. A stored function is a special type of stored program that returns a value. Unlike procedures, stored functions can be used in expressions wherever you can use a built-in function or inside of SQL statements such as SELECT, UPDATE, DELETE or INSERT. >Read full article
by Tom Mochal
Use cases are an alternative technique used to document requirements. In fact, they can be used for other purposes as well, but gathering requirements is the focus here. Use cases assume that you have a system and you have people that interact with that system. In some literature, the people interacting are referred to as "actors." Use cases describe scenarios, or stories, where the actors interact with the system in certain ways to achieve a desired result. The thought is that if you describe all of the ways that people interact with a system, including the expected results of the interaction; you will end up with a complete set of functional requirements. Use cases are especially popular with newer "light" (agile) development processes. >Read full article |
