<p>What tools are people using for testing SQL Server databases?</p>

<p>By this I mean all parts of the database:</p>

<ul>
<li>configuration</li>
<li>tables</li>
<li>column type</li>
<li>stored procedures</li>
<li>constraints</li>
</ul>

<p>Most likely, there is not one tool to do it all.</p>

[{'answer_id': 27926, 'author': 'Sean Chambers', 'author_id': 2993, 'author_profile': 'https://Stackoverflow.com/users/2993', 'pm_score': 0, 'selected': False, 'text': '<p>I personally use NHibernate with SqlCe, this provides a "throw-away" database that doesn\'t need any specialized tear down after the tests are run.</p>\n\n<p>It also provides a good way to test your nhibernate mappings if applicable.</p>\n\n<p>Here is a link to an article I wrote awhile ago on how to accomplish this: <a href="http://www.codeproject.com/KB/database/TDD_and_SqlCE.aspx?display=Print" rel="nofollow noreferrer">http://www.codeproject.com/KB/database/TDD_and_SqlCE.aspx?display=Print</a></p>\n'}, {'answer_id': 28519, 'author': 'Craig', 'author_id': 2894, 'author_profile': 'https://Stackoverflow.com/users/2894', 'pm_score': 2, 'selected': True, 'text': '<p>How do you mean "Test the database"?  </p>\n\n<p>If you are testing foreign keys, a simply script to insert invalid data is all you should need.</p>\n\n<p>Testing a database could imply a great number of issues.  Does it have all the tables?  Are the tables correct?  Are the indexes in place?  Did the latest updates get applied?  Has the data been migrated?  Is the even valid?  Are the foreign keys correct?</p>\n\n<p>There is a lot to test in a database so you are unlikely to find a simple way to test it.  I find that a combination of test stored procedures and some Nunit unit tests do most of the vetting of my databases.</p>\n'}]
['https://Stackoverflow.com/questions/27916', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/2342/']