Channel Register

Comments on: Delayed SQL Server 2008 hits release phase

What serious business purpose does 2008 serve over 2000/2005? 

Posted Wednesday 11th June 2008 01:24 GMT

Other than enrich MS?

What does it do besides new extensions (read: lockins). Why should I use it?

Why should you use it? 

Posted Wednesday 11th June 2008 07:11 GMT

Gates Horns

Because we say so! Now shut up and give us your money, cerf.

@Anonymous Coward 

Posted Wednesday 11th June 2008 07:37 GMT

Perhaps you should do a little research for yourself?

I'm no MS fan particularly but.. 

Posted Wednesday 11th June 2008 07:54 GMT

Thumb Up

Column compression and other BI improvements.. Significant tuning and configuration improvements. Unlike Vista, this is a real functional upgrade.

JFGI 

Posted Wednesday 11th June 2008 07:56 GMT

Happy

http://technet.microsoft.com/en-us/magazine/cc434690.aspx

Re: What serious business purpose does 2008 serve over 2000/2005 

Posted Wednesday 11th June 2008 08:00 GMT

Linux

>Why should I use it?

You should use it if you want your DB Apps to run slower and your DB server to consume more memory.

SQL Svr 2008 improvements 

Posted Wednesday 11th June 2008 08:09 GMT

There are a number of improvements to the reporting services elements, these might be useful if your organisation is pursuing an MS based BI strategy.

http://www.microsoft.com/sqlserver/2008/en/us/reporting.aspx

@AC 

Posted Wednesday 11th June 2008 08:42 GMT

Go

Ahh a true DB techie. We don't upgrade our software and we don't leave a huge bloody signpost saying we have been skiving off work looking at El Reg.

I salute you!

Seriously, no point at all, we will be moving to SQL Server 2005 in a few months as its now got some useful functions that would be nice to implement in general AND are actually making it into the software stack. It should be stable as its had 3 years or so to bed in ; )

Whats 2008 got over 2005 in terms of really useful stuff ? Spatial data types ... hmmm ... ummmm ... multimedia streams/types .. hmm .. errrrrrrrrrrrrrrrrrrrrrrrror

what does it do? 

Posted Wednesday 11th June 2008 08:46 GMT

I consider myself a fairly heayweight SQL Server optimiser, and I can't outperform the Merge statement. It's certainly going to be of use to stock control.

Also, the Linq front end will help the objects only sheep who've fallen for Sun's "middle tier / sell more hardware paradigm" propaganda.

It's still missing a few things though, true parallel query, for instance.

Why should you use it? 

Posted Wednesday 11th June 2008 09:07 GMT

Gates Halo

Obviously only upgrade if you need to but for me it will be the native spatial types that move me over.

Try reading a little bit before automatically assuming it doesn't bring anything new to the table.

table value parameters & Merge statement 

Posted Wednesday 11th June 2008 10:09 GMT

^^ no more silly chopping up of delimited strings or passing in bloated XML. Well worth the upgrade in my book. Spatial datatypes? seem a bit niche to me, perhaps I'm lacking imagination.

Milestone? 

Posted Wednesday 11th June 2008 10:38 GMT

Or millstone, perhaps. Sticking with Postgres.

(first-posting AC): OK, mea culpa, should have done some reading first. Apologies all 

Posted Wednesday 11th June 2008 10:52 GMT

However thanks for the feedback, most of which was constructive. Not certain there's much there outside of BI worthwhile for any but the very heaviest users (but BI users above say positive things).

Regarding merge, I don't see what it gets you (except lockin). I suppose I'll use it someday and see if I can equal it performance-wise (I too am a good optimiser).

But thanks all.

Oh, and Mr. "You should use it if you want your DB Apps to run slower and your DB server to consume more memory." - that post was about as useless and information-free as mine.

MERGE as standard 

Posted Sunday 15th June 2008 10:37 GMT

I agee with AC, thanks for the positive comments - Reg could do with more of them.

Just to add my own 2 cents worth, MERGE doesn't actually represent lock in - it is part of the SQL 2003 standard.