SQL Server Performance

DBAs Bar Door Against Big Bad .Net Wolf

Discussion in 'Please Tell Us What You Think' started by dineshasanka, Aug 29, 2005.

  1. dineshasanka Moderator

    At the heart of the problem is T-SQL, a proprietary stored procedure language that SQL Server DBAs know like the back of their hands but that might as well be Greek to most .Net developers.

    Microsoft still intends to support and innovate around the T-SQL language that developers use to build applications for SQL Server, but developers will be able to use the often faster and less code-intensive SQL CLR.

    Read More
    http://www.eweek.com/article2/0,1895,1853616,00.asp
  2. FrankKalis Moderator

    At the heart of the problem are two different mindsets. Procedural and set-based. And while it seems to be a huge problem for developers with experience in procedural client languages to get acquitant to SQL, I'm absolutely not sure that it is the correct approach to implement procedural functionalities into a RDBMS to make it easier for those developers to code. also, the quote above is a bit misleading. Microsoft still claims that SQL is the premier language to do database programming and only in such cases where SQL isn't enough, one should use the CLR...

    ...so far with the theory. I guess, in practise it will look different. A developer will stick to what he knows and if he can get the job done without having to learn a "new" language with a different approach, guess what he will do?

    Btw, I'm very curious on a proof, where the SQL-CLR is faster and less code-intensive when it comes to DML operations.

    --
    Frank Kalis
    Microsoft SQL Server MVP
    http://www.insidesql.de
    Ich unterstütze PASS Deutschland e.V. http://www.sqlpass.de)

Share This Page