RE: query tune
- From: "Mohan, Ross" <RMohan@xxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 15 Mar 2005 22:26:40 -0000
Normally I'd agree w/you Niall, but I read an article on a guru website =
(www.dbgurusecrets.com)
that told me there are internal hacks you can do in the database to make =
it "go to 11" even if
your volume control only is calibrated for 10. (But, I think you have to =
take a course to get
the info.)
Lurching Compulsively to Truncation,=20
etc.=20
-----Original Message-----
From: Niall Litchfield [mailto:niall.litchfield@xxxxxxxxx]=20
Sent: Tuesday, March 15, 2005 5:22 PM
To: Mohan, Ross
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: query tune
ah
I believe you have fallen victim to what gaja would call compulsive =
tuning disorder, mladen's suggestion will likely reduce response time to =
acceptable levels, there is no need to tune beyond this point :)
If however this were a new system it might be wise to schedule a =
truncate... drop storage; command on a regular basis as part of the =
system design. As this appears to be a web content management system I =
would suggest implementing this on the arrival of new content.
=20
On Tue, 15 Mar 2005 22:06:19 -0000, Mohan, Ross <RMohan@xxxxxxxxxxx> =
wrote:
> MG -
>=20
> Why not go all the way...and squeeze EVERY LAST DROP of performance=20
> out =3D of this query?
>=20
> TRUNCATE TABLE URL_PAGES drop storage;
>=20
> I don't understand why some DBAs just don't "cross all the T's and dot =
> =3D all the I's"
>=20
> Yours in Performance,=3D20
>=20
> etc.
>=20
>=20
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx =3D=20
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Mladen Gogala
> Sent: Tuesday, March 15, 2005 3:32 PM
> To: oracledbam@xxxxxxxxxxx
> Cc: oracle-l@xxxxxxxxxxxxx
> Subject: Re: query tune
>=20
> Seema Singh wrote:
>=20
> >Hi,
> >
> >What changes required in below query to make faster?
> >
> > =3D20
> >
> The following command will speed the query up tremendously:
>=20
> TRUNCATE TABLE URL_PAGES;
>=20
> Executing this command will speed up the query for an order of =3D=20
> magnitude. You don't have to thank me. That is all I can help you with =
> =3D without knowing the availability of indexes, distribution of data =
in=20
> the =3D indexed columns, size of the table and server version.
>=20
> --=3D20
> Mladen Gogala
> Oracle DBA
> Ext. 121
>=20
> --
> //www.freelists.org/webpage/oracle-l
> --
> //www.freelists.org/webpage/oracle-l
>=20
--=20
Niall Litchfield
Oracle DBA
http://www.niall.litchfield.dial.pipex.com
--
//www.freelists.org/webpage/oracle-l
Other related posts:
