title: Using TSQLUNIT for SQL unit testing: don't you need to duplicate your SQL code?
body: <p>I'm considering writing some unit tests for my Tsql stored procedures, I have two concerns:</p>
  
  <ol>
  <li><p>I will have to write a lot of SQL to create test fixtures (test data prepared in _setup procedures)</p></li>
  <li><p>I will have to "re-write" my query in the test procedure to obtain the results to compare against the results from the stored procedure I'm testing.</p></li>
  </ol>
  
  <p>Considering that my DB has hundreds of tables and really complex stored procedures... I don't see how this will save me time?? any thoughts? am I missing something? is there any other way to go?</p>