Anonymous

My feedback

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

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 9 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 » Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 86

    <=-=Dec 27 2010 12:13PM=-=>

    Hello Russell

    Thank you for proposing a new DCR for SQL Agent. We are always looking forward for the customer feedback. We will consider your proposal in one of our future releases.

    Thank you
    Alex Grach

    <=-=Jan 25 2011 5:04PM=-=>

    This functionality seems essential. Why won’t there be a SQL Agent Proxy? In many scenarios there is a Service Account under which all things run and that service account is normally a domain account – which may or may not have permissions to run SQLCMD or Powershell etc.

    <=-=Jan 25 2011 5:08PM=-=>

    Besides, if we run SQLCMD and the Sproc or Query errors out, the job agent steps still are marked successful. There is not robust error handling mechanism using SQLCMD from the Job Agent

    <=-=Mar 23 2011 1:23PM=-=>

    Although it is possible to “simulate a proxy” by granting impersonation rights to a proxy…

    Anonymous supported this idea  · 
  3. 775 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    61 comments  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base