|
|
Posted by Erland Sommarskog on 12/29/06 22:24
fireball (fireball@onet.kropka.eu) writes:
> well, I need to justify to my client, why to switch to sql2005 form
> 2000. I know a lot of 'why it's better', but my client don't really care
> most of those aspects.
> I need to argue, my client's business gains on that.
Since we don't know your client's business needs, we can't help you.
As David and ZeldorBlat said, if the client is happy with the system,
there is little reason to change.
But if your client is asking you to add new feature, and you can
confidently say that it would be so much easier to do with SQL 2005,
then you have a selling point. The difficult part is of course that
in many cases the difference is minor. While we as a programmer don't
want to be without row_number() or improved error handling once we've
used it, it's not really sufficient to convince the client to move on.
But here are two-three possible areas where the difference is high
enough:
1) General auditing. This can be easily be done in a generic fashion
with FOR XML and the new xml data type.
2) Any sort of queues - go Service Broker!
3) A heavy use of blobs (text/ntext/image). The new data types makes
it so much easier for you as a programmer, and thus cuts development
costs.
I could probably add a few more, but it gives you an idea what to look
for.
Of course, there will be a day when SQL 2000 reaches end-of-life support,
but it is not going to happen soon, and there might a be yet a new
SQL Server version out by then.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|