Not just TSQL for procs.
Hi all.
By now you all know that with SQL Server 2005, you (will) have the ability to write stored procedures in a wide array of languages, and not just TSQL. And MS is introducing some enhancements in TSQL as well.
But what this means is that it opens up sql server programming to a wider audience. A lot of programmers trained in C, VB etc. will be able to write for sql server.
So, throwing it open for discussion, what do you think about....
a. The quality (or lack thereof) of back-end programming that front-enders will be developing?
b. The throwing-open-of-the-doors to high temple of database programming to the masses?
I guess from the way I have worded the questions, you can tell how I feel about this. After quite some years of experience in databases, I might have committed the sin of thinking I am part of the elite; the keeper of the data, so to speak. I have seen front-enders come in and throw together views or even some TSQL code that is badly written with no care to resource utilitzation or optimization.
Also, I guess there is a bit of apprehension that the traditional power-base of dbas and sql programmers will be eroded. So far it was a very character based world, not as cool and attractive as building snappy programs and GUIs, all that will change with SQL Server 2005. Am I on the right track here, what do you think?
Thanks for reading. Cheers.
By now you all know that with SQL Server 2005, you (will) have the ability to write stored procedures in a wide array of languages, and not just TSQL. And MS is introducing some enhancements in TSQL as well.
But what this means is that it opens up sql server programming to a wider audience. A lot of programmers trained in C, VB etc. will be able to write for sql server.
So, throwing it open for discussion, what do you think about....
a. The quality (or lack thereof) of back-end programming that front-enders will be developing?
b. The throwing-open-of-the-doors to high temple of database programming to the masses?
I guess from the way I have worded the questions, you can tell how I feel about this. After quite some years of experience in databases, I might have committed the sin of thinking I am part of the elite; the keeper of the data, so to speak. I have seen front-enders come in and throw together views or even some TSQL code that is badly written with no care to resource utilitzation or optimization.
Also, I guess there is a bit of apprehension that the traditional power-base of dbas and sql programmers will be eroded. So far it was a very character based world, not as cool and attractive as building snappy programs and GUIs, all that will change with SQL Server 2005. Am I on the right track here, what do you think?
Thanks for reading. Cheers.
