Jim Mullennix

My feedback

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

    We’ll send you updates on this idea

    58 comments  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →
    Jim Mullennix supported this idea  · 
  2. 272 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  20 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Jim Mullennix supported this idea  · 
  3. 30 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Jim Mullennix supported this idea  · 
  4. 572 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    29 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jim Mullennix commented  · 

    I agree. This is a major pain for some types of migrations. Some migrations are mandated to be as quick as possible, with minimal code changes. Imagine having to update dozens to hundreds of stored procedures, views, and other SQL statements for an application that is vintage 2008 or earlier that makes heavy use of GETDATE. Every single instance of a datetime field has to be evaluated and updated and tested. This could add weeks to implementation. That could be very expensive.

    Jim Mullennix supported this idea  · 

Feedback and Knowledge Base