November 25, 2007 at 3:58 am
i have a SqlServer2000 Database with over than 1 milion records.is there any top benefit in SQL2005 to change my database ?
November 25, 2007 at 7:37 am
It really depends on what your database is used for, the 2005 version of SQL Server has some new features like the ability to rebuild indexes online, database mail, database mirroring which adds to the the "High Availability" options available to you, database snapshots which can be useful for reporting and table level restores. Do you utilises DTS in your current database? 2005 has completely new ETL product, Integration Services (SSIS). Which is built on a completely new object model so any packages you currently use on SQL Server 2000 will also need to be upgraded.
SQL 2005 ships with an upgrade advisor it would be worth running that against your 2000 server to get an idea of the work involved...also worth noting SQL Server 2008 is due for release in Feb 08.
Gethyn Elliswww.gethynellis.com
November 25, 2007 at 8:12 am
Hi dr_csharp,
Check the new features in SQL Server 2005
http://www.microsoft.com/sql/prodinfo/features/top30features.mspx
http://www.microsoft.com/sql/prodinfo/overview/whats-new-in-sqlserver2005.mspx
Make the jump to SQL Server 2005
http://articles.techrepublic.com.com/5100-9592-6036309.html
http://searchsqlserver.techtarget.com/generic/0,295582,sid87_gci1194265,00.html
http://searchsystemschannel.techtarget.com/tip/0,289483,sid99_gci1229039,00.html
Regards,
Ahmed
November 25, 2007 at 9:22 am
My recommendation would be... unless you have an immediate need for the Security enhancements, there's not much you can't do in a relatively simple manner in 2k T-SQL including Row_Number, Ranking, Percentile, etc. Wait for 2k8 sp2 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2007 at 9:26 am
p.s. And a million rows isn't much so far as SQL Server is concerned... certainly, it's not sufficient for justification of 2k5 or 2k8. I've got lookup tables that are almost that big (tele-communications) and tax records that exceed 60 million rows. SQL Server 2k doesn't miss a beat on those...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 5:38 am
The only thing I will add is that if Microsoft follows their plan to only support two versions of a product, you may find SQL 2000 support is gone as early as March of next year.
November 26, 2007 at 8:10 am
SQL Server 2000 SP4 support goes on until 2013.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
November 26, 2007 at 8:14 am
Hi Rudy,
Do you happen to have an MS URL that states that so that I can calm some of the current "panic" occurring at work?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 8:20 am
Let me look for it. I actually got the information when we had a production outage on a SQL 2000 SP3a instance in August this year and was told by PSS and our TAM that SP3a support ended July of 2007 and we needed to upgrade to SP4 which is supported to 2013. Well enough of the story, let me hunt for the link now.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
November 26, 2007 at 8:23 am
Jeff here is the link needed to help calm the 'Nervous Nellies'
http://support.microsoft.com/lifecycle/?p1=2852
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
November 26, 2007 at 8:37 am
It's paid support that goes until 2013, and you don't get "hotfixes" or things changed. That is probably not a big deal for most people in a practical sense, but from a "risk" standpoint, you might not want to pay for a hotfix agreement and if you needed something, you'd be looking at a large charge. Either from MS or from a migration effort.
A million rows isn't much at all. When you get to a few hundred million, you might think about upping hardware and changing versions.
I'd test the SS2K8 CTP and consider migrating sometime late next year if you have no compelling reasons. It will get you moving on the new CLR/DMF/SMO paradigm (among others) and get you a solid 7 years of patches/hotfixes.
November 26, 2007 at 9:38 am
Thanks, Rudy! That's exactly what I was looking for.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 9:53 am
Glad to be able to help.
Have a great day Jeff !
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply