Settings and activity

9 results found

  1. 7 votes
    How important is this to you?
    Wesley Smith shared this idea  · 
  2. 20 votes
    How important is this to you?
    Wesley Smith supported this idea  · 
  3. 16 votes
    How important is this to you?
    An error occurred while saving the comment
    Wesley Smith commented  · 

    David,

    SQL Source control generates code that checks @@ERROR after each statement and inserts into #tmpErrors when an error occurs. This is then used at the end of the script to decide to COMMIT the transaction.

    The migration script doesn't have that code after each statement. So, if some operation of the migration script were to fail, the SQL Source control doesn't know about the error and will just continue to the end of the script, where it will commit the changes. I'd like some way for the script to detect an error in the migration script and not commit.

    Wesley Smith shared this idea  · 
  4. 1 vote
    How important is this to you?
    Wesley Smith shared this idea  · 
  5. 9 votes
    How important is this to you?
    Wesley Smith shared this idea  · 
  6. 3 votes
    How important is this to you?
    Wesley Smith shared this idea  · 
  7. 135 votes
    How important is this to you?
    under review  ·  Elizabeth Ayer responded

    Hi – this request was closed when the ‘TFS work items’ feature was released. http://documentation.red-gate.com/display/SOC3/Committing+changes

    However, we’re still hearing about this enough that I’d agree with commenter Ben: it should be reopened.

    We will continue to gauge interest here on UserVoice. Please do tell us more in the comments about what you expect to be able to do with Work Items in SQL Source Control.

  8. 189 votes
    How important is this to you?
    Wesley Smith supported this idea  · 
  9. 47 votes
    How important is this to you?
    Wesley Smith supported this idea  ·