Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Oracle Searches

  • 24-08-2000 2:54pm
    #1
    jd
    Registered Users, Registered Users 2 Posts: 5,741 ✭✭✭



    "This, I'm told, is disabling the indexes on that field and making the search
    slow."

    yip, its going to do a full table scan...

    "Theres a lot of rows (10,000+) but that shouldnt really affect a supposedly
    top-notch database like oracle should it?"


    10000 rows is shag all. have you properly tuned the database. if it was like 'jhjhj%' it would use the index..
    what kind of times are you geting from the sqlplus prompt

    john




Comments

  • #2
    jd
    Registered Users, Registered Users 2 Posts: 5,741 ✭✭✭jd



    "what kind of times are you geting from the sqlplus prompt2#"

    btw for comparison I get this from a fairly random table with
    2244508 rows


    1* select count(*) from te_cdkeys where cdkey like '%555%'
    SQL> /

    COUNT(*)
    11766

    Elapsed: 00:00:06.71


    jd


  • #3
    DeVore
    Business & Finance Moderators, Entertainment Moderators Posts: 32,387 Mod ✭✭✭✭DeVore


    Calling any oracle experts,

    We have a query on an oracle database which is holding free text areas.
    There are a lot of rows and the text is quite large. We're using " ...WHERE
    fieldname LIKE '%blah%' " to match against any row whose text-field
    contains the substring 'blah' anywhere in it.

    This, I'm told, is disabling the indexes on that field and making the search
    slow.

    Whats weird is that we used the same SQL against an old access database and
    it was quite quick.
    Same database, same rows, everything just about the same.

    Anyone got any suggestions as to how we speed it up?
    Theres a lot of rows (10,000+) but that shouldnt really affect a supposedly
    top-notch database like oracle should it?

    This one has me stumped I have to admit. Thoughts?

    Tom.



Advertisement