Is there any inherent problem in calling the obsolete object from SSL? I have been engaged with a problem that I want to use a stored procedure to solve completely, do I need to worry about using wet objects against writing in CLR based language ?
Just make sure that you can not do this as a set-based operation first, to free them Remember to do this when you do, and remember that it will not be all portable (but then neither CLR code.)
Comments
Post a Comment