[dba-SQLServer] SQL 2005 Server Management Studio

>> My understanding is that SQL Server uses VB.NET as it's internal
scripting language which opens up what you can do with Stored procedures.
Not quite true. SQL 2005 includes the .NET framework in its installation and
permits you to use either VB.NET and C#.NET in stored procedures. But MS
itself says the new languages are not intended to replace TSQL, which
remains the principal language for sprocs and UDFs. It is emphatically not
recommended to rewrite all your stored procedures using these languages.
These language extenstions are intended for special-case situations, in
particular when working with row-by-row logic, and when writing to multiple
target tables from within a sproc, where the concept of a recordset may be
useful. TSQL can do these sorts of things but the syntax is clumsy. Note
also that the .NET languages impose a performance penalty. Equivalent TSQL
will run more quickly.
Finally, I think that the presence of .NET languages in SQL Server will
probably result in a bunch of .NET developers thinking that they know how to
manipulate a SQL Server. In other words, there will be a LOT of work
available in a year or so for TSQL experts, increasing the performance of
code written in .NET.
Arthur