Linked by Thom Holwerda on Wed 21st Sep 2005 14:48 UTC, submitted by kellym
.NET (dotGNU too) Specialized programming languages and their supporting environments have always been tightly coupled: SQL and the database; business rules and the rules engine. It's tempting to wish for an überlanguage or one syntax to rule them all, but what really matters is a common environment. At its 2005 Professional Developers Conference, Microsoft showed that it's finally putting all of its eggs into the .Net basket.
Thread beginning with comment 35223
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: SQLJ
by jayson.knight on Thu 22nd Sep 2005 22:55 UTC in reply to "RE[2]: SQLJ"
jayson.knight
Member since:
2005-07-06

Huh? Moving things like sorts away from the database is actually a very good thing (unless the column has a clustered index on it). Would you rather have 1000 concurrent clients doing a large sort on a server, or 1000 concurrent users sorting a set of data locally?

Reply Parent Bookmark Score: 1

RE[4]: SQLJ
by on Fri 23rd Sep 2005 17:18 in reply to "RE[3]: SQLJ"
Member since:

In this case the clients with good performing hardware will benefit and clients with old hardware will suffer alot. Is this a step forward?? Not really. 1000 sorts by a 1000 persons isn't that much in a large scale application. Databases have highly optimized code to do this. Might depend on what databases we're talking about. And also, If the client is a webserver would you rather have the webserver doing stuff like sorts, instead of serving webpages? Another problem is the huge amount of unecessary network traffic you'll get.

Reply Parent Bookmark Score: 0