"Joe Spears" <joespears@hotmail.co.uk> wrote in message
news:u4mag.156498$tc.56861@fe2.news.blueyonder.co.uk...
> Hi
> I'm trying to put a case together to encourage my employer to upgrade from
> its SQL 2000 Enterprise farm to SQL Server 2005.
>
> We're interested in Enterprise functionality, such as:
> - Improvement in backups
> - Monitoring improvements
> - Resilience improvements (mirroring, replication, failover etc).
> - Cost / payback case.
>
> Can anyone point me in the right direction to be able to put together such
> a case.
>

>
> "Joe Spears" <joespears@hotmail.co.uk> wrote in message
> news:u4mag.156498$tc.56861@fe2.news.blueyonder.co.uk...
>> Hi
>> I'm trying to put a case together to encourage my employer to upgrade
>> from its SQL 2000 Enterprise farm to SQL Server 2005.
>>
>> We're interested in Enterprise functionality, such as:
>> - Improvement in backups
>> - Monitoring improvements
>> - Resilience improvements (mirroring, replication, failover etc).
>> - Cost / payback case.
>>
>> Can anyone point me in the right direction to be able to put together
>> such a case.
>>
>
>
>
> What's New in SQL Server 2005
> http://www.microsoft.com/sql/prodinfo/overview/whats-new-in-sqlserver2005.mspx
>
> There's lots of cool stuff:
> Mirroring.
> Monitoring performance with Server reports and DMV's.
> Transactional Replication.
> The new database maintence plan desiner is great.
> Database Mail.
> SSIS.
>
> But what does your organization struggle with? Stories that start
> "Remember when we had that problem ...", help motivate the upgrade. Heve
> a concrete vision for how SQL Server 2005 fits in your environment.
> That's the business case.
>
> David
>
>