Select performance

Is it fair to say that it takes no time (compared to the nested SELECT) to make the second (outer) ‘SELECT’ from a result-set like this?

    SELECT some_column 
    FROM
         (
           SELECT some_column
           FROM some_table
         )
    AS _alias

  • Using cast in SQL with multiple column selections
  • Fetch history of records
  • Keeping a SQL Server Database Project and the Actual Database (in SSMS) in sync during development
  • The values of one column cannot be greater than another
  • Drop all extended properties on SQL Server
  • Gaps and Islands query / reset row count based on column seqeunce
  • Using a .MDF SQL Server Database with ASP.NET Versus Using SQL Server
  • Variable assignment is not allowed in a statement containing a top level UNION, INTERSECT or EXCEPT operator
  • How to include loan rules in Employee and Loan sql query?
  • Add Values to Grouping Column
  • Is there a way to tuneup a complex count query against heavy data?
  • SQL Server 2008, pivot with no aggregate fuction
  • One Solution collect form web for “Select performance”

    The SQL optimizer is likely to treat that SELECT statement as if it was written:

    SELECT some_column FROM some_table
    

    So there’ll be no performance difference whatsoever. The optimizer does its best to minimize the cost of producing the answer and will rework the query you write to speed things up. Only the most na├»ve optimizer would evaluate the inner SELECT and save the results in a table and then run the outer SELECT on that result.

    MS SQL Server is a Microsoft SQL Database product, include sql server standard, sql server management studio, sql server express and so on.