|
February, 2006
In
This Issue
|
|
All articles have been reprinted with the written consent of their respective authors. | ||||||||||||||||
|
||||||||||||||||
|
Remote Procedures Calls in Oracle by James F. Koopmann Often times we want to get information from a different Oracle instance than the one our current application is running on. Often times the information can only be gotten by having a procedure execute on the other instance. Getting the SYSDATE of another machine is just one situation. Here is an installment I call "Remote Procedure Calls Will Get You the Cheese".
Click here
for the article. | ||||||||||||||||
|
||||||||||||||||
|
Do the Simple Things First Simplification is an imperative in this day and age of increasing complexity and ever-changing software environments. A key component of simplification, in my opinion, is to remember the basics and apply some simple rules and practices to our DB2 subsystems and applications. Indeed, many troubles surface because we don’t keep track of things we already know. This principle is backed up in the recent best-selling book Blink: The Power of Thinking Without Thinking by Malcolm Gladwell (published by Little, Brown, 2005, ISBN: 0316172324). Through the use of case studies and examples Gladwell introduces us to the power of our "adaptive unconscious" – a powerful innate ability that provides us with instant and sophisticated information. Basically, it boils down to using our experience to arrive at quick decision that are usually correct. As I read this book I pondered how its nuggets of wisdom could be adapted to how we manage DB2 systems. So, what are the basics that we should always keep top-of-mind? Let’s examine some of the primary issues and concepts that need to be addressed in order to keep a DB2 implementation humming along.
Click here
for the article.
|
||||||||||||||||
|
||||||||||||||||
|
Introduction to Service Broker Service Broker is the new kid in the block in SQL Server 2005. Before we actually delve into the features of Service Broker and write our first program, let us first imagine a scenario where we would want to fit Service Broker and then work off that. It is often a common requirement for applications to execute processes in an asynchronous fashion. We see it all around us. For example, if you go to any online book store and order for a book, you do not wait for the order to be completed and shipped. Rather, your request is queued and then processed at a later point in time and you are free to do your other shopping. How are these applications built? The following graphic shows a simple schematic of such an application. Click here for the article.
In A Nutshell
Interested in learning more tips and techniques for SQL Server? "In A Nutshell"
is what you are looking for. Kevin Kline,
author of O'Reilly's "SQL in a Nutshell" and "Transact-SQL Programming" and President of The Professional Association for SQL Server,
offers tips, techniques and much more. Updated numerous times a week,
there is always valuable material to be had!
Click
here
to see what Kevin is up to in the SQL Server world. | ||||||||||||||||
|
||||||||||||||||
|
The MySQL 5.0 Archive Storage Engine More than at any other time, database professionals are being aggressively challenged by mushrooming volumes of data in corporate business systems. While some industry analysts project data growth at an average rate of 42% a year, that figure is conservative in some installations where growth rates are several hundred percent, with no end in sight. What's to blame for sky-rocketing data volumes? First, corporations have realized the golden nugget potential of all the data floating around in their transactional systems and are utilizing data warehousing more than ever before. The strategic use of data is high on the mind of nearly every CIO and business executive, so in response, transactional data is stockpiled into data warehouses where business intelligence users constantly aim their analytic queries to produce forecasts that are used to make key business decisions.
Click here for the article. | ||||||||||||||||
|
||||||||||||||||
You have all heard the mantra of scope change management – make sure that all scope change requests get approved by the sponsor (or sponsor designee). This should be obvious for large scope change requests. However, it is not always practical to gain individual approval for every five, ten or twenty hour scope change request. However, you definitely need to have a way to capture and manage these requests. If you don’t, you will quickly find that you are dealing with the infamous “scope creep”. There are three techniques to employ for managing small scope changes. Click here for more information on these techniques. | ||||||||||||||||
|
||||||||||||||||
|
Webcasts
| ||||||||||||||||
|
||||||||||||||||
|
||||||||||||||||
|
||||||||||||||||
|
Interactive Crossword
Puzzle: "Seeing Red"
|
||||||||||||||||
|
||||||||||||||||
|
We love getting white papers, tips, articles, and code examples/archives from our readers around the world. Send your submission to newsletter@quest-pipelines.com. If your article is published, it will be mailed to over 28,000 subscribers. Our mission at Quest Software - RevealNet Labs is to anticipate the daily responsibilities and challenges faced by database professionals. Our products help thousands of people solve problems and implement solutions every day. This newsletter is designed to help facilitate the sharing of information among database professionals. About the Newsletter This newsletter is distributed to Quest Software - RevealNet Labs customers, prospects and friends who have subscribed to it from our website. If you would like to unsubscribe, please visit http://qlist01.quest.com/UnsubMailingList/ Subscribe a Friend! Do you know someone who would like to receive the Pipeline Newsletter? If so, please enter their email address in the box below and click SUBMIT.
Past Issues of the Pipeline Newsletter |
||||||||||||||||
