Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7600267
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 30, 20262026-05-30T22:52:12+00:00 2026-05-30T22:52:12+00:00

When I use many WITH clauses in query, it executes longer, rather than without

  • 0

When I use many WITH clauses in query, it executes longer, rather than without it.
Query structure like this:

with t1 as (select some_fields from table1 inner join table2),
     t2 as (select some_fields from t1 inner join table3),
     t3 as (select some_fields from t2 inner join table4)
select * from t3

What approach should be used for optimization of similar queries?
In my case each subquery returns about 10 million rows.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-30T22:52:14+00:00Added an answer on May 30, 2026 at 10:52 pm

    With all the secrecy involved I suggest you to take a look at EXPLAIN PLAN for both queries. In my opinion WITH is nothing more than syntax sugar allowing you to reuse certain sql in subqueries. But in all it’s usefulness it doesn’t always lead to the most efficient plan.

    and yes, 10 000 000 is always gonna be slow.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I want to use many bars like this one in my app (i don't
Kind of like this question I have many text snippets that I use many,
I use only classes and never use IDs. Many people like to use IDs
I've seen people use many-to-one mappings to represent one-to-one relationships. I've also read this
This article on MSDN states that you can use as many try catch blocks
This is a follow up question to this one: Query examples in a many-to-many
How can I use XPath to select a node without retrieving all of its
I have the SQL query: select title, scale / next_scale, c from ( select
If I use many CLOB variables in the PL/SQL stored procedure to store many
With C# 3.0 you could use many of its features (object initializers, var variables,

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.