hitzand

My feedback

  1. 106 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    hitzand supported this idea  · 
  2. 11 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    hitzand supported this idea  · 
  3. 19 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  17 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    hitzand commented  · 

    Same error here on 2016 after applying SQL 2016 SP2.

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

    We’ll send you updates on this idea

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

    Upvotes: 6

    <=-=Sep 3 2017 8:30PM=-=>

    I can confirm that the Dimensions with Dynamic security defined FAIL to [Process Update] after applying the KB4019916 patch.
    For example the following MDX expression is used in the Dimension Data “Allowed Member Set” to restrict members based on the USERNAME – a [Process Update] on this dimension FAILS, even immediately after a successful [Process Full] has been performed:
    Allowed Member Set:
    EXISTS}, “User Security”)

    Prior to applying KB4019916 windows update a [Process Update] on this dimension was completing successfully.

    hitzand supported this idea  · 
  5. 1,300 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    48 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    hitzand supported this idea  · 
  6. 346 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Upvotes: 249

    <=-=Oct 4 2016 2:15PM=-=>

    This is similar to my feedback located here: https://connect.microsoft.com/SQLServer/feedback/details/2769130/sql-2016-temporal-tables-with-triggers. The solution I suggest is similar to this, and could be used in many different cases developing using SQL server.

    <=-=Jan 10 2017 9:43AM=-=>

    I would love this too. The issue is that many/most applications don’t use Windows Auth in the connection to SQL Server (connection pooling issues, etc), so SQL can’t get the User information

    <=-=Jan 10 2017 9:51AM=-=>

    @Sanford

    Just to clarify, I am not asking for an “automatically store user name” feature. I’m asking for “automatically store whatever I want, based on whatever expression I provide.” So the fact that the user name may or may not be available is not really relevant.

    That said, there are plenty of workarounds for various situations. I imagine that if you’re using a shared connection, you can get some notion of “user” some other…

    hitzand supported this idea  · 
  7. 472 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    18 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    hitzand supported this idea  · 

Feedback and Knowledge Base