jrstern

My feedback

  1. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  (General Feedback) » Other  ·  Flag idea as inappropriate…  ·  Admin →
    jrstern shared this idea  · 
  2. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Diagnostics and Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
    jrstern supported this idea  · 
  3. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure portal » Dashboards + tiles  ·  Flag idea as inappropriate…  ·  Admin →
    jrstern shared this idea  · 
  4. 15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    jrstern shared this idea  · 
  5. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    jrstern commented  · 

    There are three or four or five different Azure services that provide some sort of scheduling of things, but none is even as easy to use as SQL Agent - which is itself rather crude, as these things go. We want the ability to run a TSQL script directly. I understand there *is* already something more like SQL Agent already in alpha or beta test today, so I'm not going to waste a vote here. I've just started using Azure Web Jobs as a replacement, but I have to wrap everything in a little C# console app just to get it to run.

  6. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback here.

    SQL Trace is one of our older SQL Server technologies that’s on the path for deprecation. XEvents is the modern replacement. I’d love to learn more about your scenario here. Please reach out to me. Query Store is another alternative.

    Thank you
    Guy.

    jrstern commented  · 

    SQL Trace/Profiler is still the gold standard for monitoring and performance tuning. XEvents is supposed to be the modern replacement and much more efficient than old-style tracing - but XEvents was about 50% completed in SQL 2008 and has been left that way since. It is also much more complex to use, and still very poorly documented or supported. It would be great if Azure could lead the way on providing 100% (or more!) of the old SQL Trace/Profiler functionality, based on XEvents, in a new, and easy to use format.

    Query Store is not the same kind of thing, nor is the Plan Cache on which Query Store is based. However, it may be that technically (if I can speculate), a little extension of the Plan/Query store would be a *better* basis for a SQL Trace replacement, than is XEvents.

    jrstern supported this idea  · 

Feedback and Knowledge Base