Amy

My feedback

  1. 298 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    42 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    From Apr 24, 2019 (https://cloudblogs.microsoft.com/sqlserver/2019/04/24/sql-server-management-studio-ssms-18-0-released-for-general-availability/):
    Think of these two tools not as separate tools doing different things, but as one integrated tool. Each tool has different experiences built into it and can be launched from the other seamlessly.

    From Oct 20,2020 (https://cloudblogs.microsoft.com/sqlserver/2020/10/20/sql-server-management-studio-18-7-now-generally-available/):
    SQL Server Management Studio is a foundational tool for many working with Microsoft data solutions. First released in 2018, Azure Data Studio is a cross-platform and open source desktop environment for data professionals using the Azure Data family of on-premises and cloud data platform solutions. Architecturally, SQL Server Management Studio has long been combined with additional tools, including Profiler, Database Engine Tuning Advisor (DTA), and Database Mail. As Azure Data Studio continues to mature, the Microsoft data tools experience on Windows has become a combination of SSMS and Azure Data Studio. Beginning in the 18.7 release of SQL Server Management Studio, Azure Data Studio…

    Amy supported this idea  · 
  2. 12 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 125

    <=-=Aug 10 2007 9:17PM=-=>

    Hi Microsoft, please confirm this optimizer problem by running the scripts, it is self evident and can be optimised significantly better.

    Eg. For a minimum, the optimal plan is to obtain the minimum for each partition using the index and then taking the minimum of all the (partition) results. The same principle can apply to maximum, and for Top N over an index …

    The plan should stand out as optimal, because the number of reads over the index is very small, and there will be one set of page reads (usually only one page) for each partition…. you can use the assumption that the number of partitions is significantly smaller than the number of rows (or even count the number of partitions), to estimate the cost (page reads) – which comes out at about N pages where N is the number of partitions.…

    Amy supported this idea  · 
    An error occurred while saving the comment
    Amy commented  · 

    Please fix.

Feedback and Knowledge Base