Discussion on:

5
Comments

Join the conversation!

Follow via:
RSS
Email Alert
http://techrepublic.com.com/5138-9592-5823770.html

Are you planning to upgrade to SQL Server 2005 or are you still evaluating? What aspect of the updated version do you find most interesting?

Is there something about SQL Server that the TechRepublic should know in addition to the 10 we've listed?{/b]
0 Votes
+ -
MS has promised that we would be able to develop stored procedures for this version without having to use T-SQL... this will allow more flexibility for developers and less reliance on specialists.
Personally, I found this article less than useful. With all the flaws (outlined below), I simply didn't walk away with a significantly better knowledge of what SQL Server 2005 will do for me than when I started reading. So here are my problems:

First, don't assume that every developer reading this uses and is familiar with every last aspect of SQL Server that there is. For example, what's "WAITFOR" for the person who's never heard of it? Sure we can go look it up in SQL Help, but I shouldn't have to cross-reference significantly while reading an article.

What if you're strictly a low-level developer and don't use DTS commonly? I've used DTS several times myself, but I know other developers who have used it only minimally or not at all, preferring to simply write their own SQL code from the ground up, or who simply aren't versed enough to know what it does. You should give a brief outline of what it does in 2003 vs. what it does in 2005.

Second, you need examples of what these features mean to the developer. Queries can be recursive...great...how does that help me? I understand what recursion is, and I can see possible benefits of it for something like a corporate directory, but show me examples of the original table data and the output of the query. Telling me I can use it in a WITH clause of a SELECT, ...etc. query is a little vague without a concrete example to understand it by.

Finally, this obviously cleared a spell-check, but it didn't clear a "does this make sense?" check. I spotted several different places where the word was obviously wrong but was phonetically similar ("incursion" instead of "recursion", for instance...I don't think we're declaring war on our queries), or was at least suspect "in" instead of "and" in the last para of point 2.
It was planned to introduce exception handling in T-SQL for the 2005 release of SQL Server, any news on that?

PL/SQL has had this very useful language feature for decades...

NT
Great Article! Well explained.Examples may add more value to this post. you can find some basic overview about SQL server 2005 features here http://www.techbubbles.com/sql-server/sql-server-2005-features/

Keyboard Shortcuts:
Prev
Next
Toggle
Join the conversation
Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]

Join the TechRepublic Community and join the conversation! Signing-up is free and quick, Do it now, we want to hear your opinion.