>>>>>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.
>>
>>It will be taken out and replaced by who knows what :(
>
>Replace the whole database??? Then they should be knowing what they are doing, moving away also the "built-in" functions.

Yes. There is still a chance, as they are going to take another look next year, so I might still convince them it is the right approach :) On the other hand, the same system is using another technology they do not like (SQL Service Broker, the .NET procedure is the one I use to read the SB queue) they want to replace it with a product similar to MSMQ, so... they might decide to scrap it all