Jörg Debus

My feedback

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

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Jörg Debus shared this idea  · 
  2. 150 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  8 comments  ·  SQL Server » Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Jörg Debus 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  ·  SQL Server » Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Jörg Debus shared this idea  · 
  4. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Jörg Debus supported this idea  · 
  5. 8 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 →
    An error occurred while saving the comment
    Jörg Debus commented  · 

    This bug is a good old friend. It never worked as expected by simply use the URI-notation. The technical reasons for the problem are:

    1) many SQL-tools see the (localdb) as a remote linked server that does not support links from other SQL Server instances and therefor don't search for it correctly. E.G. SQLCMD connects to a shared instance of (localdb) if the named pipe address is used like "np:\\.\pipe\LOCALDB#SH85B09E\tsql\query"

    2) The owner of the shared instance and the account of the caller and the security settings for the instance data must be the same.

    Jörg Debus supported this idea  · 
  6. 20 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 » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jörg Debus commented  · 

    This is a fully reproducible bug in all versions of SQL Server 2016 LocalDB installations. So handling this bug only after having received UP-votes is inadequate handling of bugs.

    This is not an idea or a recommendation.

    Jörg Debus supported this idea  · 

Feedback and Knowledge Base