visual studio solution configuration rights

I'm trying to find a solution to prevent my dev开发者_StackOverflow中文版eloppers team running the solution configuration "release" which contains the production settings. I just want to prevent careless error like "OMG, I was in Release configuration during my test, I delete all the database" or something like this...

We are working on Visual Studio 2010 with TFS. I was wondering if there is a right to use a specific type of solution configuration and not an other...

If you know an other way to be sure this kind of error will never append, I'll take it too! ^^

Thanks in advance

---

As John suggested, you should limit access to your production database first. Next, you could have your release configuration error out if a particular environment variable isn't defined. Just check for that environment variable before you zap the database.