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


Is It Worth Upgrading to SQL Server 2008


Is It Worth Upgrading to SQL Server 2008

Author
Message
daggles
daggles
Valued Member
Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)

Group: General Forum Members
Points: 53 Visits: 249
from planning our company migration from 2k5->2k8, it looks like it will at least be easier than our 2k->2k5 migration :-)
peter-757102
peter-757102
SSC Eights!
SSC Eights! (861 reputation)SSC Eights! (861 reputation)SSC Eights! (861 reputation)SSC Eights! (861 reputation)SSC Eights! (861 reputation)SSC Eights! (861 reputation)SSC Eights! (861 reputation)SSC Eights! (861 reputation)

Group: General Forum Members
Points: 861 Visits: 2559
SQLMadness (12/18/2009)
We are currently upgrading from SQL Server 2005 to 2008. One major factor in our decision to upgrade was Filtered Indexes.


Yup, this is the feature I earely want to use and will help a lot in typical applications.
ssaroia
ssaroia
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 3
Upgrade to 2008 because its code base may be different than 2005 and you will get efficient processing and support from Microsoft. Microsoft may have improved code otherwise they will not ask you to upgrade. Look the way we develope and maintain our applications.

Also if you want to get Enterprise features of 2008 later then you will be ready and there will be no downtime and re-testing.
warefore
warefore
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 10
Thx for working thru features vs cost. My client's application has been SQLS/2k for 5 years; no upgrade in the original license AFAIK, so several thou $ to consider SQLS/05, so I had not even looked at it. Now, it seems that if it ain't broke w/SQLS/2k, then "fixing" it w/any subsequent version is not worth the $Cool ... or any more time reading thru 9 pages of commentsHehe.
JStiney
JStiney
SSC Journeyman
SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)

Group: General Forum Members
Points: 95 Visits: 446
SQL 2008 Compression and Table Partitioning are not to be underestimated. They have allowed us to easily justify going to Enterprise Edition instead of Standard Edition when we upgrade from SQL 2000.
Our two largest databases BUDGET_HOURLY and BUDGET have been reduced in space used for the data files (mdf files) from 531 Meg to 106 Meg and 239 Meg to 44 Meg. In the BUDGET_HOURLY database all tables were compressed and in BUDGET database we compressed only tables with more than 10 million rows. The table partitioning greatly improved nightly index rebuild times on the largest tables, and the applications is running significantly faster.
SQL Server 2008 is running as a virtual machine under Hiper-V, but on a faster box than the SQL 2000 so comparing run times gets complicated. Suffice to say, we are very happy with the results of moving to SQL 2008 Enterprise on a virtual machine. We really did not think we could justify Enterprise Edition until we did the testing, but we had the machine and we had the time, and the results far exceeded our expectations.



tlampl
tlampl
Forum Newbie
Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: General Forum Members
Points: 2 Visits: 29
John S. meant GB (not meg).



JStiney
JStiney
SSC Journeyman
SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)

Group: General Forum Members
Points: 95 Visits: 446
There is an error in the database sizes from my previous post, should be Gig not Meg.
(531 Meg to 106 Meg and 239 Meg to 44 Meg) should be (531 Gig to 106 Gig and 239 Gig to 44 Gig).
It would be difficult to justify Enterprise Edition if the databases were that small.



William-317219
William-317219
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 4
I imagine most companies will move to SQL Server 2008 because of the off-box key management features the Enterprise version provides. Anyone that has to pass a PCI-DSS audit will definitely appreciate that feature, along with the other encryption artifacts.
Tom Thomson
Tom Thomson
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14554 Visits: 12238
Good article, and much interesting discussion.

The outfit I ran until the middle of last year will be going to SQLS 2008, despite it not being much different from 2005 - but won't be going to 2005. Having not yet upgraded from SQLS 2000 Std edition, the upgrade is now going to be direct from SQLS 2000 to SQLS 2008, skipping 2005. Then the app environment will be upgraded to the latest .net version and use WPF and XAML.

Being a small outfit with customers to whom IT is generally regarded as a cost to be minimised meant we didn't have the option of upgrading a customer's SQL servers during the contract or of using a more expensive MS licensing model that would allow the customer's systems to be upgraded for free.

The one after SQLS 2008 will probably be skipped too, for the same reasons - unless there's a real zoom in the target market that allows a lot of growth.

Tom

Steve Jones
Steve Jones
SSC Guru
SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)

Group: Administrators
Points: 64587 Visits: 19118
Tom,

I think a lot of companies are looking at things this way. Some may even skip SQL 2008 and R2 from 2005 to jump to 2011 or 2012 since it has not been that long since SS2K8 was released.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
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