Reputation: 13277
I'm running a classic asp app that's migrating to a .NET 4.0 app; it mostly does CRUD and some reporting (currently not via Reporting Services). I don't do many other kinds of remote jobs - the most I do is a simple replication of one table to another on the same server.
Is it worth going to 2008 given this scenario?
Upvotes: 0
Views: 66
Reputation: 432271
SQL Server 2005
Go with SQL Server 2008 of course.
Upvotes: 0
Reputation: 64645
I guess I'm in the minority on this one. IMO, given what little you have told us, the reason for going up to 2008 would be a smooth upgrade path.
If you do not need data compression ( only in the Enterprise version BTW ), or do not need intellisense since you are using something else ( e.g. Visual Studio ) to build your queries or do not need adding CPUs on the fly ( because a quick reboot is acceptable ) then SQL 2008 probably will not provide enough benefit to justify the additional cost (again depending on your licensing situation). At some point, 2005 will become "ancient" technology (probably Nov 2011 when SQL Server 2011 comes out) and that might make things difficult from a feature set/support standpoint for developers. If you can wait until November until Denali is supposed to be released, then I would do that.
Upvotes: 0
Reputation: 754518
If you're starting fresh and have options - you might also want to consider:
SQL Server 2005 is officially "end of support" as of April 2011. Personally, I wouldn't pick that version anymore, over 2008 or 2008 R2.
Upvotes: 0
Reputation: 106
Yes.
Upvotes: 3
Reputation: 13549
2008 is easier to develop in (intellisense). It also makes it easier to use things like Reporting Services, Analysis Services, and Integration Services.
2005 is totally fine for the scenario you've got, it's still a premium quality server.
Upvotes: 0
Reputation: 1981
Whether it is worth the upgrade dependes on what you value.
I would move to 2008 just to get the new features, bug fixes, and tools.
Upvotes: 0