<p>What is the best way to use SQL Server 2008 as a development database, but ensure that the database is compatible with SQL Server 2005?</p>

[{'answer_id': 7547, 'author': 'vzczc', 'author_id': 224, 'author_profile': 'https://Stackoverflow.com/users/224', 'pm_score': 5, 'selected': True, 'text': '<p>This can be done via SQL Enterprise Manager or like this:  </p>\n\n<pre><code>ALTER DATABASE &lt;database&gt; \nSET COMPATIBILITY_LEVEL = { 80 | 90 | 100 }\n</code></pre>\n\n<p>Use 90 for 2005 compatibility.  </p>\n\n<p>This replaces the functionality used for previous releases, the stored procedure <em>sp_dbcmptlevel</em>.</p>\n'}, {'answer_id': 39109, 'author': 'mrdenny', 'author_id': 4197, 'author_profile': 'https://Stackoverflow.com/users/4197', 'pm_score': 3, 'selected': False, 'text': "<p>You can set the database compatibility level, but there is no guarantee that this will cover all your bases.  For example the new data types will be available on the SQL 2008 system, but they won't be available on the SQL 2005 server.</p>\n\n<p>The only way to guarantee that everything will work from Dev to Prod is to put SQL 2005 in development.</p>\n"}, {'answer_id': 122043, 'author': 'Cade Roux', 'author_id': 18255, 'author_profile': 'https://Stackoverflow.com/users/18255', 'pm_score': 0, 'selected': False, 'text': "<p>Don't forget that there are also behavioral differences between the two versions, and something on 2008 may perform differently (and insufficiently) than 2005 all other things equal - this will obviously depend on a lot of factors about your data and application.</p>\n\n<p>You're better off developing against the lowest common denominator and testing against the newer versions.</p>\n"}]
['https://Stackoverflow.com/questions/7535', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/708/']