RE: *****SPAM***** RE: Differences between Oracle and Progress, actually starting point for considering any migration from Oracle to anything else...
- From: "Richard J. Goulet" <rgoulet@xxxxxxxxxx>
- To: <mark.powell@xxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 20 Mar 2007 13:55:20 -0400
That's funny at a minimum and absolutely absurd at the other. How do
you account for the delay time on the stopwatch button caused by the
person holding the stopwatch?
........................................................................
.............................................................
Kanbay
Dick Goulet, Senior Oracle DBA
45 Bartlett St | Marlborough, MA 01752 USA
Tel: 508.573.1978 | Fax: 508.229.2019 | Cell: 508.742.5795
rgoulet@xxxxxxxxxx
........................................................................
.............................................................
On February 8, 2007 Kanbay was acquired by Capgemini, one of the world's
leaders in consulting, technology and outsourcing services, employing
nearly
68,000 people in North America, Europe, and the Asia Pacific region.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Powell, Mark D
Sent: Tuesday, March 20, 2007 1:23 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: *****SPAM***** RE: Differences between Oracle and Progress,
actually starting point for considering any migration from Oracle to
anything else...
While using a physical stopwatch is a valid end to end timing method
(from customer enter to response), this method definitely lacks
precision for timing individual database operations. I can see some
humor in running across this recommendation.
-- Mark D Powell --
Phone (313) 592-5148
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jeremiah Wilton
Sent: Tuesday, March 20, 2007 11:37 AM
To: nigel_cl_thomas@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: *****SPAM***** RE: Differences between Oracle and Progress,
actually starting point for considering any migration from Oracle to
anything else...
A brief look at the tuning section Progress OpenEdge RDBMS manual
reveals that it also sports a sort of wait event interface, making it
competitive with Oracle. I had to read it several times, because I
thought "stopwatch"
was an OpenEdge technical term. I was wrong.
From the Database Essentials manual:
http://www.psdn.com/library/servlet/KbServlet/download/1906-102-2517/gsd
be.p
df
Collecting your baseline statistics
Once you have determined what items you want to benchmark, you can plan
your strategy. You can modify the application code to collect this data,
which is the most accurate method, but it is also time consuming and
costly. An easier way to perform data collection is to time the
operations on a stopwatch. This is fairly accurate and easy to
implement. To determine the best timing baseline for each task, perform
timing in isolation while nothing is running on the system. When timing
baselines have been established, repeat the task during hours of
operation to establish your under-load baselines.
Absolutely hilarious.
:-)
Regards
Jeremiah Wilton
ORA-600 Consulting
http://www.ora-600.net
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Nigel Thomas
The OP specifically asked about the PROGRESS database (see
www.progress.com), not PostGres. To be specific, I think it is Progress
OpenEdge RDBMS http://www.progress.com/openedge/products/index.ssp (ie
not ObjectStore, omne of their more recent acquisitions).
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
