Matthias Kurz

My feedback

  1. 3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 6

    <=-=Jul 9 2007 12:51PM=-=>

    Dupe of:

    https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124624

    <=-=Jan 22 2008 2:09PM=-=>

    Kurt,
    Thanks for your valuable feedback and sorry for the late answer. As you might have seen in the community discussion comment of your submission, there is a related suggestion about the same issue. We are planning to implement this feature in our next major release. This other suggestion also includes a possible workaround, see https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124624
    With best regards,
    Roman

    <=-=Apr 5 2010 3:12PM=-=>

    Hi,
    I have resolved your request as duplciate of feedback item below:

    https://connect.microsoft.com/SQLServer/feedback/details/124728


    Umachandar, SQL Programmability Team

    Matthias Kurz commented  · 

    Are there plans to implement this?

    Matthias Kurz supported this idea  · 
  2. 3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 106

    <=-=Apr 20 2006 7:33PM=-=>

    As a further example, consider flushing the contents of an ADO.NET dataset to the database server. Currently, the order of the updates is critical. It would simplify code design if you could just a) start a transaction b) send all the updates c) commit them.

    <=-=Oct 13 2006 1:35PM=-=>

    Hello Greg,

    Thanks for the feedback. We are aware of this and looking into it for a future release.

    Sameer Verkhedkar
    SQL Engine
    [MSFT]

    <=-=Apr 9 2008 5:07AM=-=>

    This is a duplicate of feedback id 124624.

    The SQL ANSI-92 standard is to defer constraint checking until the commit phase – only 16 years ago now.

    It is not a question of performance or faster dev, it is a fundamental to any database to be able to change a record from one consistent state to another consistent state within a transaction,…

    Matthias Kurz commented  · 

    Any plans so far to implement this?

    Matthias Kurz supported this idea  · 
  3. 88 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  4. 20 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Azure Database for PostgreSQL » Extension  ·  Flag idea as inappropriate…  ·  Admin →

    Microsoft announced acquisition of Citus Data and its ongoing commitment to open source. Stay tuned for product roadmap announcements. For more information see these blog posts:

    Announcement: https://blogs.microsoft.com/blog/2019/01/24/microsoft-acquires-citus-data-re-affirming-its-commitment-to-open-source-and-accelerating-azure-postgresql-performance-and-scale/

    More on how Citus will be integrated into Azure Database for PostgreSQL: https://azure.microsoft.com/en-us/blog/microsoft-and-citus-data-providing-the-best-postgresql-service-in-the-cloud/

    From the founders of Citus Data: https://www.citusdata.com/blog/2019/01/24/microsoft-acquires-citus-data/

    Matthias Kurz supported this idea  · 
  5. 3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Azure Database for PostgreSQL » Extension  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  6. 8 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  7 comments  ·  Azure Database for PostgreSQL » Extension  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  7. 2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Database for PostgreSQL  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  8. BDR

    6 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Azure Database for PostgreSQL  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  9. 5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Azure Database for PostgreSQL  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  10. 5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Azure Database for PostgreSQL  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  11. 12 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Azure Database for PostgreSQL  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  12. 11 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Database for PostgreSQL  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  13. 23 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Azure Database for PostgreSQL » Extension  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  14. 22 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Database for PostgreSQL  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  15. 63 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Azure Database for PostgreSQL » Roadmap  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  16. 46 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  10 comments  ·  Azure Database for PostgreSQL  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 
  17. 5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz commented  · 

    @Schuyler Rosefield readonly SESSION_CONTEXT variables are only reset when you close a connection - or not? Does this mean for each user you have a own connection? Or can you somehow reset a readonly SESSION_CONTEXT variable?

    Matthias Kurz supported this idea  · 
  18. 6 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Active Directory » End user experiences  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz commented  · 

    Same here

    Matthias Kurz supported this idea  · 
  19. 80 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    22 comments  ·  Azure portal  ·  Flag idea as inappropriate…  ·  Admin →
    Matthias Kurz supported this idea  · 

Feedback and Knowledge Base