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/
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.
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.
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.
Discuss This Question: 3  Replies