Nobody

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

    under review  ·  1 comment  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Nobody commented  · 

    Correction: datetime pickers no longer respect the request header as in previous versions, they now always use a date format matching the RDL's Language element. Unfortunate decision, but at least some control is possible.

    Nobody shared this idea  · 
  2. 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 →

    Upvotes: 63

    <=-=Jan 27 2009 11:44AM=-=>

    Thank you for submitting this request. We do intend to enable localization of parameter prompts in a future release of SQL Server but it is not yet scheduled work.

    <=-=Feb 5 2009 6:19PM=-=>

    Thank you for submitting this request. We do intend to enable localization of parameter prompts in a future release of SQL Server but it is not yet scheduled work.

    <=-=Mar 24 2009 7:49AM=-=>

    Yes, it would be very interesting to add this functionnality.
    In fact, it seems that it was enabled in pre-release versions. See post from Teo Lachev at http://prologika.com/CS/blogs/blog/archive/2007/10/18/parameterized-parameter-prompts.aspx and his confirmation that it was removed at http://prologika.com/CS/forums/t/897.aspx.
    Right now I can localize everything as described by Laurie Tuschen but the parameters prompt. For me it’s a big issue as I could not find any other way to make it work. I tried:

    1) To use report code…

    Nobody 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

    under review  ·  0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Nobody shared this idea  · 
  4. 93 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  5 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Nobody commented  · 

    Second usecase has been problematic - and prone to classic 'runs for months then breaks' Errors- until 2012 with the advent of TRY_CONVERT...

  5. 0 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 →
    Nobody commented  · 

    Many objects in SSRS already have a 'dependent objects' tab, although not all work properly. The usecase is important enough that I have had a *report* for this for a decade. Select from ReportServer.dbo.Catalog self-joining ItemID to LinkSourceID and filtering a little...

  6. 76 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 » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Nobody commented  · 

    Easy enough. T-SQL jobstep using exec msdb.dbo.sp_start_job, potentially dependent on some select from msdb.dbo.sysjobhistory.

  7. 9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Nobody shared this idea  · 

Feedback and Knowledge Base