This is an old thread, but I'd like to offer an alternative viewpoint from
outside of the pure technology related answers given here, which are quite
valid as presented, and offer a viewpoint from the managment/economics
perspective.
The other point to consider in this type of upgrade scenario is the /cost/
of delaying the upgrade.
Currently you have a production server up and running, and you're obtaining
new hardware. Presumably you'll have adequate time to install, configure,
and test the new server before doing the switch-over from the old server.
Now, you have two choices:
(1) Invest in, and upgrade to, SQL Server 2005 now, and never have to
worry about upgrading this server for some time, or
(2) Clone the existing SQL Server 2000 environment onto the new
hardware, and then, sometime during the next 2-3 years (depending on how
important it is to have a 'supported' database in your production
environment), you will need to upgrade to SQL Server 2005.
The key question here is what will be the /cost/ of doing this upgrade on a
production server later, vs doing the upgrade on a 'new' server now.
[quoted text, click to view] "Andrew Watt [MVP - InfoPath]" <SVGDeveloper@aol.com> wrote in message
news:nud7k1p0vorf2t3t67dph9li0o5du4rfme@4ax.com...
> On Tue, 4 Oct 2005 08:34:18 -0400, "DLG" <deanl144@hotmail.com.nospam>
> wrote:
>
>> We are getting ready to get a new server (lease is up on the old one) and
>>we currently have a license for SQL 2000 and this software meets our needs
>>so I am currently planning on using the existing license on the new
>>server.
>>However, I am thinking that since we are going to get new hardware we may
>>as
>>well get new software but I am not sure of how I can justify to my boss
>>the
>>additional cost. Could someone provide me some real world experience? The
>>server will typically be used for internal corporate web applications with
>>50-200 users.
>>thanks
>>
>
> If your current software meets all your business needs then I would
> suggest that there is no need to upgrade immediately.
>
> On the other hand, there is an enormous number of new features in SQL
> Server 2005. Take a look at
>
http://www.microsoft.com/sql/2005/default.mspx > and, in a few weeks, think about spending a few dollars on a Developer
> Edition copy of SQL Server 2005.
>
> Whether or not upgrading to SQL Server 2005 is worthwhile for your
> company depends on your business needs.
>
> Andrew Watt
> MVP - InfoPath
