fireball写道： 好吧，我需要证明我的客户，为什么要切换到sql2005表格2000.我 知道很多'为什么它更好''，但我的客户不要我真的非常关心那些方面。 我需要争辩，我的客户的业务收益就是这样。 提前Thnaks。
坦白说，你的客户是对的。为什么你认为他们应该b / b 切换？哦，对，你不知道。如果你不知道那么 不可能是一个令人信服的理由。你有2000年的b $ b问题吗？您的 客户端是否希望您只能在2005年实施？如果你不能回答这些问题，那么就没有理由升级 - 或者，从客户的角度来看， ，花钱要升级。
fireball写道： 好，我需要证明我的客户，为什么要切换到sql2005形式2000.我 知道很多'为什么它'更好''，但我的客户并不在乎大部分 那些方面。 我需要争辩，我的客户的业务收益就是这样。 提前提醒。
如果他们对现有系统感到满意，那么现在可能没有多少理由可以切换。 如果他们想要进行新的开发或添加新的 应用程序，或者如果他们可以利用 他们的一些新功能，请考虑升级现有系统（例如镜像）。 - David Portas，SQL Server MVP 尽可能请发布足够的代码来重现您的问题。 包含CREATE TABLE和INSERT语句通常会有所帮助。 说明您正在使用的SQL Server版本并指定内容 的任何错误消息。 SQL Server联机丛书： msdn2.microsoft/library/m...S,SQL.90).aspx -
火球（fi******@onet.kro pka.eu）写道： 好，我需要证明我的客户，为什么要切换到sql2005表格 2000.我知道很多'为什么它更好''，但我的客户并不在乎 大部分方面。 我需要争辩，我的客户的业务收益。
由于我们不了解客户的业务需求，我们无法帮助您。 正如David和ZeldorBlat所说，如果客户对系统感到满意， 没有理由改变。 但是如果你的客户问你添加新功能，你可以自信地说，使用SQL 2005会更容易， 那么你有一个卖点。困难的部分当然是 在很多情况下差别很小。虽然我们作为一名程序员并不希望想要没有row_number（）或改进错误处理，一旦我们使用了b $ b，它就不是真的足以说服客户继续前进。 但这里有两个三个可能的差异很大的区域 够了： 1）一般审计。这可以通过FOR XML和新的xml数据类型以通用的方式轻松完成 。 2）任何类型的队列 - 去Service Broker ！ 3）大量使用blob（text / ntext / image）。新的数据类型使得作为程序员对你来说更容易，因此削减了开发成本。 我可能会增加一些，但它会让你知道看什么。 . 当然，有一天会有SQL 2000到达生命终结支持， 但它不会很快发生，到那时可能还有一个新的 SQL Server版本。 - Erland Sommarskog，SQL Server MVP， es **** @ sommarskog.se SQL Server 2005联机丛书 www.microsoft/technet/pro...ads/books.mspx SQL Server 2000联机丛书 www.microsoft/sql/prodin f ... ons / books.mspx
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. Thnaks in advance.
解决方案 fireball wrote: 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. Thnaks in advance.Quite frankly your client is right. Why do you think they should switch? Oh, right, you don''t know. If you don''t know then there couldn''t possibly be a compelling reason to do so. Have you had problems with 2000? Is there some feature in an application that your client wants that you can only implement with 2005? If you can''t answer those questions then there''s really no reason to upgrade -- or, from your client''s perspective, spend the money to upgrade.
fireball wrote: 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. Thnaks in advance.If they are happy with their existing system then there perhaps isn''t much reason to switch right now. Consider upgrading if they want to do new development or add a new application or if they can take advantage of some new features with their existing system (mirroring for example). -- David Portas, SQL Server MVP Whenever possible please post enough code to reproduce your problem. Including CREATE TABLE and INSERT statements usually helps. State what version of SQL Server you are using and specify the content of any error messages. SQL Server Books Online: msdn2.microsoft/library/m...S,SQL.90).aspx --
fireball (fi******@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, es****@sommarskog.se Books Online for SQL Server 2005 at www.microsoft/technet/pro...ads/books.mspx Books Online for SQL Server 2000 at www.microsoft/sql/prodinf...ons/books.mspx
更多推荐
争论为什么sql2005
发布评论