Top 5 relational data warehouse performance improvements you would like to see in next version of SQL Server

Hello Everyone,

We are currently looking at top performance issues for various workloads and how we can improve those in next version of SQL Server. We are collecting feedback from various customer sources. I would like to extend an invitation to readers here for feedback on top 5 relational data warehouse performance improvements you would like to see in SQL Server.

Please bear the following in mind:

1. Briefly describe the relational data warehouse workload or scenario or application. More details you can provide for us the better.

2. Prioritize the list of performance improvements in order of importance or impact to your workload. You can also just highlight the top 5 performance problems with running your relational data warehouse workload in SQL Server

3. Feel free to suggest any feature(s) that will help in improving the performance of the particular data warehouse workload or scenario

I will consolidate the feedback and post summary version of it as a link in this post.


Comments (13)

  1. Are you Datamart Builder with few bones to pick? Are your cubes too slow?Ok, so I can’t do anything to…

  2. EHO says:

    Please solve SQL 2000 problem 469591 ("When using sp_cursoropen with an Order By Clause we Generate an Inefficient plan ")

  3. EHO says:

    please ignore my posting from September 25, 2006 11:43 AM

    wrong category

  4. If you use SQL Server and have a great suggestion for performance improvements to the engine then post…

  5. It would be really nice if you improved the sql processor to do better type casting.  I have taken to always doing explicit casts in all of my WHERE clauses to avoid the potential for very small queries.  An example is when doing a query with the where clause including a bit column.

    SELECT *

    FROM persons

    WHERE enabled = 1 –enabled is a bit column

    In this case the query will scan through each row in persons, cast the enabled column to an int and then compare it to the value 1.This can be very slow.  I always do a cast in this case

    ie :WHERE enabled = CONVERT(bit,1)

    But many people do not and this presents a problem.  I have noticed that SQL Server 2005 and 2000 behave very differently here.  Sometimes 2005 gets it right when 2000 gets it wrong, and sometimes 2000 gets it right when 2005 gets it wrong.

    This just seems like a really easy optimization.

  6. Dave says:

    Can we have some unsigned int datatypes?

  7. Dave says:

    Can we have some unsigned int datatypes?

  8. PP says:

    Not sure if I can call this as DW improvements.  But for sure I can say, if you guys can provide a URL where you guys can post "Case Studies" explicitly describing

    1. Nature of Problem

    2. What was accomplihsed

    3. Technology used

    4. What was the performance growth

    5. User base (# of users)

    6. Network Topology


    May be this information is missing across web & I have been searching a lot on this, but noluck

  9. susie dba says:

    a) Can we have some unsigned int datatypes?

    b) Can we have some unsigned tinyint datatypes?

    c) Can we have some unsigned smallint datatypes?

    d) seperate date and time datatypes

    e) ability to remove custom datatypes from a large existing database easily

  10. aaron kempf says:

    better mdx design-time tools

    better mdx query support in ms access

    able to backup natively to a compressed format

    ability to save your database diagrams into another format so that you can print them and format them– instead of buying erwin and spendning a month to recreate your model

    simple data entry and reporting forms

    ability to KEEP CONNECTIONS OPEN in .NET… we typically use @@SPID as a session identifier; and your stupid ‘we cant keeep connections open’ theory is a total PITA

  11. sqletips says:

    General note. Please do not post general feature requests. We are looking specifically for performance issues only.

    For example, there were several posts asking about unsigned int data types. Why do you need unsigned data types? How do you think it will improve performance of your application?

    Also, we are asking for relational data warehouse performance improvements only not Analysis Services.



  12. joeydj says:

    BI studio is a centralize tool for designning

    SSIS package and everything

    can we have an SSIS automation engine

    which serves as a centralize engine

    for managing and monitoring SSIS packages

    an engine where we can deploy all our package

    link the packages in specific order and

    from there see which package has failed and what was wrong.

    if something did went wrong the engine allows me to execute the next package in the link

    or something that allows me to start anywhere

    in the link of packages

    from that engine we can see everthing that went wrong to that package or link of packages including things like server is down. tlog is full etc

    wish for a centralize automation and monitoring tool for SSIS package which is

    as powerfull as the Bi design studio.


  13. Julian-Kuiters says:

    There’s been some interesting questions by users on the SQL Server Engine Tips blog. While almost all of them seem to be off topic, there are some interesting ideas. One of the fun ones was from Dave asking "Can we have some unsigned int data types?" So assuming Dave is wanting unsigned integers for this reason, I created a blog entry on how you would

    create unsigned integer user datatypes

    in SQL Server 2005…

Skip to main content