>And of course, it's probably an SP3 or maybe SQL Server 2008 change when the marketing >folks bring us SQL# to allow us to deploy SQL code into .NET applications...