This post originated from an RSS feed registered with .NET Buzz by Paschal. Original Post: Locking a database design, is it really possible ? Feed Title: help.net Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/pleloup/Rss.aspx Feed Description: .Net for mankind ! Latest .NET Buzz Posts Latest .NET Buzz Posts by Paschal Latest Posts From help.net

I wish I could see some improvements in the future version of SQL Server and .Net about their dependances.

I try to explain. In SQL Server if something happen to one of your database, whatever the catching error system you implement, you finish all the time by broken your beloved .Net application.

A good example is the identity field which is linked to an index key. This is a typical case where if you destroy the index, you lose the identity feature, and kaboom you trigger by accident an error on your application.
This is also true if you import export tables from one server to another.

Is it possible with Yukon to 'lock' the database design ? I like the Apple way to implement a lock in OS X settings, where you can lock/unlock the panel (if you are the administrator) and then up to you to change what ever you want.

Today I know I can implement some triggers in my database, but if you look at the big picture I think it could be a good idea to protect some long hours of database design.