>>That is not a problem when the DBA is you :)
>
>But it can bite you in the future. I was the DBA, had beautiful .NET code on SQL, when our IT department merged with parent company, I stopped being DBA and the .NET code suffered an awful fate :)

I don't understand why .Net code would suffer.