Upgrade to SQL Server 2005 sooner or later?

Backup and Recovery
Database Management Systems
IT architecture
SQL Server
Standard Edition 2000
Version 7 and earlier
Hello, I'm the editor of SearchSQLServer.com and I am hoping to get your opinons on a timely topic. Prior to Microsoft announcing its November 7 release date for SQL Server 2005, we had run a poll asking site members: How have the delays with SQL Server 2005 affected your organization's plans? 58% delays had no affect 28% projects were being held up 13% may start considering other platforms You can view the poll here: http://searchSQLServer.com/r/0,,43739,00.htm? I'm wondering where you fell in -- if the delays have had any affect on your organization or opinion of Microsoft in general -- and what your plans are now that the date has been announced. Will you upgrade right away? Will you wait until all the kinks are worked out? Will you not upgrade at all and move to another DBMS instead? Please let me know when you have a moment. Comments will be included in a featured article on SearchSQLServer.com. Thank you for your time! Best regards, Robyn Lorusso Editor SearchSQLServer.com https://searchsqlserver.techtarget.com/

Answer Wiki

Thanks. We'll let you know when a new response is added.

The delay(s) have really had no effect in our organization. Yea, there are some new features in SQL 2005 that would be nice to have but we haven’t really bet the farm on any of them. If anything and I may or may not speak for a large majority, we have just become more deeply dependent on SQL 2000. We just find ways to make 2000 work for us. In my opinion most of the folks I know that use SQL 2k have become just that much more comfortable with the product (2K) and so it will just be longer before anybody will make a move to put SQL2005 into their daily routine, much less production. Sure we have been poking around with the betas, but since no one really knew when the product would come to light it was more of an exercise of curiosity than planning an upgrade. I think that until Microsoft says that they will be “laying SQL2000 to rest” and considers those that use it less of a priority will we see a strong desire to upgrade. There are a lot of successful companies that are using 2000 right now and with whatever success those companies have survived the tech bust of the early 2000’s why would they be in a hurry to fix something that ain’t broke, so to say. I think there are other priorities in business right now. At least in the middle market (SMB). I think where you will see the biggest change in adoption is with the higher market because SQL2005 is certainly a viable competitor now with the likes of Oracle and DB2 in that arena. Not that it necessarily wasn’t before (had to cover myself with that previous statement) but 2005 certainly alters the playing field now.

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Swilliamson
    We just discussed this topic yesterday with our DBA's. The concensus was that until we had a project or vendor that/who required SQL 2005 that we really couldn't justify an upgrade. The bottom line is ROI.
    0 pointsBadges:
  • SteveMalc
    Right now, SQL 2000 is working well for us (we also use Oracle and IBM DB2 Universal) so there is no great rush to move. Additionally, our business processes are highly time-sensitive and we are loathe to put something new into production without a great deal of testing. We'll probably do some testing to see if there is any impact to our applications in moving to SQL 2005. Once theat's been dealt with, we'll still wait for the first service pack to come out before it goes into production. We'll start with low volume, low impact apps first, then move in more as we gain confidence with the new version.
    30 pointsBadges:
  • Worker1
    The delay of the release has not impacted our organization. We have no plans to rush right into new versions. Usually wait a few months after release before beginning any testing. Then perform extensive testing before production implementation.
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: