SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server 2005: Changing the Paradigm


SQL Server 2005: Changing the Paradigm

Author
Message
RSP
RSP
Mr or Mrs. 500
Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)

Group: General Forum Members
Points: 520 Visits: 623
Comments posted here are about the content posted at temp



Roger L Reid
Roger L Reid
Mr or Mrs. 500
Mr or Mrs. 500 (528 reputation)Mr or Mrs. 500 (528 reputation)Mr or Mrs. 500 (528 reputation)Mr or Mrs. 500 (528 reputation)Mr or Mrs. 500 (528 reputation)Mr or Mrs. 500 (528 reputation)Mr or Mrs. 500 (528 reputation)Mr or Mrs. 500 (528 reputation)

Group: General Forum Members
Points: 528 Visits: 166

I bought this book when it first came out, because it's among the good ones.

The part I can't stand is the title. SQL Server 2005 is indeed a good release - the first industrial strength release of a product that was pretty poor until the SP3 release for 2000, and even then only if running on Windows 2003.

Now MS has an excellent product in the same league with Sybase, and for sure, with lots of free extras (whether you wanted the Ginzu Knives or not). But this is not a "paradigm change". Every time anyone releases a major version of software, there is a huge addition of features. That is marketing, not a "paradigm change".

In his intro, the anonymous corporate author from SE says "...to enhance the availability,scalability, security, and reliability of the server. This paradigm shift..."

Availability, scalability, security, and reliability are "paradigm shifts"? Excuse me, SQL Server 2000 increased those 4 factors over SQL Server 7. Sybase 11 increased them over Sybase 10 (not to mention Sybase has always been, since the 4.2 days that MS used to understand RDBs, all of those things - but they had the advantage of running on a stable OS, something the SQL Server team did not have access to before Windows Server 2003).

The claim of "paradigm shift" is silly. It's a great product, it comes with a lot of goodies - a LOT of goodies (of course you'll still need to buy or write software for monitoring and diagnosing the server) and on Windows 2003 Enterprise 64-bit running on Opterons with direct connected iSCSI arrays, it can SCREAM!

That's not a "paradigm shift". That's why we BUY the new releases of things. MS finally delivered a professional quality database system. Yep, I'll buy that. I'll even port off Sybase to avoid supporting two systems. But a paradigm shift? Plu-leaze.



Roger L Reid
RSP
RSP
Mr or Mrs. 500
Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)

Group: General Forum Members
Points: 520 Visits: 623

Thank you for reading the article, and appreciate your comments.

You said you liked the book, right? Hey, I reviewed the book's content, not the title

However, indeed as the title suggests, it was I believe the author's intent to convey the revolutionary changes to the core SQL Server Product itself, away from the notion of being just a backend database engine, to a full-scale BI platform. Since it was an early adopter and review of the product before its release, it was an introduction to technology and business professionals of a product that has fully matured, expanded, and broke free of the stereotype of that it was subpar to other industry db platforms. That way of thinking was meant to change with the release of SQL2K5, and conforms with the notion of a "Paradigm Shift" See definition below.

Think of a Paradigm Shift as a change from one way of thinking to another. It's a revolution, a transformation, a sort of metamorphosis. It just does not happen, but rather it is driven by agents of change.

Regards, Robert Pearl





Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search