Increase no. of disks, so that io will be less.

Hi,

Recently i have read an article, if the performance is slow because of full table scan.
Then we need to increase the no. of disks.? so the io will be less.

how to do this? by doing this how the performance will improve.
sakthikumarAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
having "more disks" translates into "possible to read data in parallel from several disks"

the translation of the "recommendation" could be done by either having the oracle database files on a SAN  or NAS (where then the SAN  spreads the file over several disks as needed) or explicitly by creating a tablespace with several files, each file on a different disk (which again my be san-based ...)

however, controlling the table to be spread equally over the different files in the tablespace is not easy in some cases, it may be possible by partitioning the table,

next point is: full table scan on really large tables should be exceptional (though "normal" for some datawarehouse tables), and should be reviewed in terms of "how to do it", by splitting up the work into smaller chunks. but that is then another question (and worth several weeks of high-level sql tuning trainings)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Geert GOracle dbaCommented:
if performance is slow then it's in 96% of the time ITSS
> It's The Stupid Sql (or It's The Slow Sql)

Tune the slow sql and the performance will get better

the fastest way to find the bad queries is by listing v$sql by consumed resources
buffer gets or physical reads per execution
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.