Soft Parse
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6

Thread: Soft Parse

  1. #1
    Join Date
    May 2009
    Posts
    32

    Soft Parse

    Hi All,

    When I was going through some stuff online, I have found that soft parse's reduces the scalability of an system and a SQL statement should be more likely parsed once and executed many times. I am kind of confused over here, soft parse will always consume less resources and less time-memory latches which is a good thing and more over many dba's expect the session connecting to database issue sql statements that are already present in shared pool, so can you please explain why many soft parses would reduce the scalability of the system. Thanks in advance for your help.

  2. #2
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,554
    You are correct when you say soft parses are better than hard parses nevertheless a soft parse would do syntax and security checks which is a time consuming process - not as bad as a hard parse, of course.
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

  3. #3
    Join Date
    Oct 2006
    Posts
    175
    If its a hard parse, then it needs to go through different checks, right from the syntax of the statement to the availability of the object in question and to the privileges of the user running the statement, making it cpu intensive. If a statement is found the shared pool, then it takes all these information from there skipping the above steps, making it use lesser cpu. Despite all the these good things, if a statement remains in shared pool, it increases the number of LATCH there. As the latches serialized its bound to wait, which can decrease scalability of your application as the number of transaction increases.

    HTH

  4. #4
    Join Date
    Oct 2008
    Location
    Chandigarh, India
    Posts
    322
    though it is simple but I would have never been able to relate it with scalability of application. Great gtcol!
    lucky

  5. #5
    Join Date
    Mar 2001
    Location
    India
    Posts
    58
    Soft parse is better than hard parse in all type of resource consumption.
    Thanks and Regards,
    Gitesh Trivedi
    Dbametrix Solutions
    Database DBA support

  6. #6
    Join Date
    May 2009
    Posts
    32
    Great response, thank you fellows for your replies. I would also like to share that when session_cached_cursors set, soft parsing can be reduced, resulting in reducing the cpu overhead for parsing the sql already present in shared pool.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width