Andrey Tyurin

My feedback

  1. 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 » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 2

    <=-=Aug 12 2010 8:42AM=-=>

    Thank you for reporting this behavior, we will investigate for consideration in a future release.

    Regards,
    Mike Wachal
    SQL Server

    <=-=Aug 12 2010 8:49AM=-=>

    Thank you for looking into this. Can you offer a workaround? Should I drop data collection and re-add it?

    <=-=Aug 12 2010 9:03AM=-=>

    This issue appears to be described in http://support.microsoft.com/kb/971640/ and was fixed in Cumulative Update 3 of SQL Server 2008 SP1. You can either use the information in the article to obtain the most current cumulative update (I believe it is CU9) or you can wait for the next service pack which should be available within the next several months as it is currently in it’s Community Technology Preview. Details about the CTP of the service pack are available at http://support.microsoft.com/?kbid=979450.

    Regards,
    Mike Wachal
    SQL Server

    <=-=Sep 20 2010 2:47PM=-=>

    Hello,

    Were you able to determine if…

    Andrey Tyurin commented  · 

    I'm getting this error on Microsoft SQL Server 2014 (SP3-CU3) (KB4491539) - 12.0.6259.0 (X64)

  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 » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Andrey Tyurin shared 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 » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Andrey Tyurin shared this idea  · 

Feedback and Knowledge Base