blocks|key|1502993|text|请注意，许多真正的杀手级功能只有在企业版中才有。数据压缩和备份压缩是我最喜欢的两个工具之一--它们可以立刻给你带来免费的性能提升。数据压缩减少了您必须执行的I/O量，因此许多查询的速度提高了20-40%25。CPU使用率在上升，但在当今的多核环境中，我们通常有更多的CPU能力，但没有更多的IO。不管怎么说，这些都是企业版的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1502994|如果您只打算使用Standard+Edition，那么大多数改进都需要对您的应用程序代码和T-SQL代码进行更改，因此这并不是那么容易实现的。|1502995|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Be aware that a lot of the really killer features are only in Enterprise Edition. Data compression and backup compression are among two of my top favorites - they give you free performance improvements right off the bat. Data compression lessens the amount of I/O you have to do, so a lot of queries speed up 20-40%. CPU use goes up, but in today's multi-core environments, we often have more CPU power but not more IO. Anyway, those are only in Enterprise.

If you're only going to use Standard Edition, then most of the improvements require changes to your application code and T-SQL code, so it's not quite as easy of a sell.

blocks|key|1718259|text|我在PASS+2008上参加了一堆SQL+Server2008的演讲，在我看来，唯一的“杀手级功能”就是扩展事件。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1718260|有很多巨大的改进，但这是唯一接近成为我游戏规则改变者的改进。表值参数和合并可能是我的下一个最爱。在日常生活中，IntelliSense是一个巨大的胜利。但这并不是SQL+Server2008所特有的，只是SQL+Server2008工具集(其他工具可以提供与SQL+Server2005、2000等类似的IntelliSense+)。|1718261|entityMap|0|LINK|mutability|MUTABLE|url|http://summit2008.sqlpass.org/|1|http://en.wikipedia.org/wiki/IntelliSense^0|2|9|0|0|1J|C|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

I went to a bunch of SQL Server 2008 talks in <a href="http://summit2008.sqlpass.org/" rel="nofollow noreferrer">PASS 2008</a>, the only 'killer feature' from my point of view is extended events. 

There are lots of great improvements, but that was the only one that got close to being a game changer for me. Table value parameters and merge were probably my next favourite. Day-to-day, <a href="http://en.wikipedia.org/wiki/IntelliSense" rel="nofollow noreferrer">IntelliSense</a> is a huge win.. But this isn't really specific to SQL Server 2008, just the SQL Server 2008 toolset (other tools can give you similar IntelliSense against SQL Server 2005, 2000, etc.).

blocks|key|1718047|text|有了新的features+added。但是，你将不得不看看它是否值得升级。不过，也有一些不错的improvements+in+Management+Studio+2008，特别是查询编辑器的智能感知。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1718048|entityMap|0|LINK|mutability|MUTABLE|url|http://www.microsoft.com/sqlserver/2008/en/us/overview.aspx|1|http://www.simple-talk.com/sql/learn-sql-server/management-studio-improvements-in-sql-server-2008/^0|4|E|0|1B|12|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

There are new <a href="http://www.microsoft.com/sqlserver/2008/en/us/overview.aspx" rel="nofollow noreferrer">features added</a>. But, you will have to see if it is worth the upgrade. Some good <a href="http://www.simple-talk.com/sql/learn-sql-server/management-studio-improvements-in-sql-server-2008/" rel="nofollow noreferrer">improvements in Management Studio 2008</a> though, especially the intellisense for the Query Editor.

blocks|key|1718224|text|SQL2008还允许您在特定表上禁用锁升级。我发现这在经常更新的小型表上非常有用，在这些表中，锁可能会升级，从而导致并发问题。在SQL2005中，即使在delete语句上使用ROWLOCK提示，也可以升级锁，从而导致死锁。在我的测试中，我开发的一个应用程序在小表操作期间由于SQL+2005上的锁升级而出现了并发问题。在SQL2008中，这个问题消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1718225|记住处理大量行锁的潜在开销仍然很重要，但是可以选择在需要时停止升级是非常有用的。|1718226|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

SQL 2008 also allows you to disable lock escalation on specific tables. I have found this very useful on small frequently updated tables where locks can escalate causing concurrency issues. In SQL 2005, even with the ROWLOCK hint on delete statements locks can be escalated which can lead to deadlocks. In my testing, an application which I have developed had concurrency issues during small table manipulation due to lock escalation on SQL 2005. In SQL 2008 this problem went away.

It is still important to bear in mind the potential overhead of handling large numbers of row locks, but having the option to stop escalation when you want to is very useful.

blocks|key|1718344|text|我最喜欢的一种是过滤索引。现在，我可以为最关键的查询创建覆盖索引的闪电般的速度，而对DML语句的影响很小。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1718345|/Håkan绕线器|1718346|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

One of my favourites are Filtered indexes. Now I can create lightning fast covering indexes for my most critical queries with only minor impact on DML statements.

/Håkan Winther

blocks|key|1718424|text|SQL+Server+2008引入了四种新的日期和时间数据类型，其中包括：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1718425|*+DATE:+As+you+can+imagine,+the+DATE+data+type+only+stores+a+date+in+the+format+of+YYYY-MM-DD.+It+has+a+range+of+0001-01-01+through+9999-12-32,+which+should+be+adequate+for+most+business+and+scientific+applications.+The+accuracy+is+1+day,+and+it+only+takes+3+bytes+to+store+the+date.
*+TIME:+TIME+is+stored+in+the+format:+hh:mm:ss.nnnnnnn,+with+a+range+of+00:00:00.0000000+through+23:59:59:9999999+and+is+accurate+to+100+nanoseconds.+Storage+depends+on+the+precision+and+scale+selected,+and+runs+from+3+to+5+bytes.
*+DATETIME2:+DATETIME2+is+very+similar+to+the+older+DATETIME+data+type,+but+has+a+greater+range+and+precision.+The+format+is+YYYY-MM-DD+hh:mm:ss:nnnnnnnm+with+a+range+of+0001-01-01+00:00:00.0000000+through+9999-12-31+23:59:59.9999999,+and+an+accuracy+of+100+nanoseconds.+Storage+depends+on+the+precision+and+scale+selected,+and+runs+from+6+to+8+bytes.
*+DATETIMEOFFSET:+DATETIMEOFFSET+is+similar+to+DATETIME2,+but+includes+additional+information+to+track+the+time+zone.+The+format+is+YYYY-MM-DD+hh:mm:ss[.nnnnnnn]+[%2B%7C-]hh:mm+with+a+range+of+0001-01-01+00:00:00.0000000+through+0001-01-01+00:00:00.0000000+through+9999-12-31+23:59:59.9999999+(in+UTC),+and+an+accuracy+of+100+nanoseconds.+Storage+depends+on+the+precision+and+scale+selected,+and+runs+from+8+to+10+bytes.|code-block|syntax|javascript|1718426|http://soft-engineering.blogspot.com/|offset|length|1718427|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|11|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|T|8|@]|9|@$I|U|J|V|1|W]]|A|$]]|$1|K|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|H]]]]

SQL Server 2008 introduces four new date and time data types, which include:

<pre><code>* DATE: As you can imagine, the DATE data type only stores a date in the format of YYYY-MM-DD. It has a range of 0001-01-01 through 9999-12-32, which should be adequate for most business and scientific applications. The accuracy is 1 day, and it only takes 3 bytes to store the date.
* TIME: TIME is stored in the format: hh:mm:ss.nnnnnnn, with a range of 00:00:00.0000000 through 23:59:59:9999999 and is accurate to 100 nanoseconds. Storage depends on the precision and scale selected, and runs from 3 to 5 bytes.
* DATETIME2: DATETIME2 is very similar to the older DATETIME data type, but has a greater range and precision. The format is YYYY-MM-DD hh:mm:ss:nnnnnnnm with a range of 0001-01-01 00:00:00.0000000 through 9999-12-31 23:59:59.9999999, and an accuracy of 100 nanoseconds. Storage depends on the precision and scale selected, and runs from 6 to 8 bytes.
* DATETIMEOFFSET: DATETIMEOFFSET is similar to DATETIME2, but includes additional information to track the time zone. The format is YYYY-MM-DD hh:mm:ss[.nnnnnnn] [+|-]hh:mm with a range of 0001-01-01 00:00:00.0000000 through 0001-01-01 00:00:00.0000000 through 9999-12-31 23:59:59.9999999 (in UTC), and an accuracy of 100 nanoseconds. Storage depends on the precision and scale selected, and runs from 8 to 10 bytes.
</code></pre>

<a href="http://soft-engineering.blogspot.com/" rel="nofollow">http://soft-engineering.blogspot.com/</a>

blocks|key|1718516|text|在过去的几个月里，Denver+SQL+Server用户组已经就SQL+2008的新功能做了一些非常好的演讲，包括Paul+Nielsen上周刚从雷蒙德的"Jump+Start“回来不久(如果我没记错的话)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1718517|关于SQL2008的所有“新特性”的一些警告，确定哪些特性将出现在不同版本中的筛选仍在进行中。许多/大多数新的/非常酷的功能，如数据压缩、分区索引、策略等只会出现在企业版中。除非您计划运行企业版，否则CTP中的许多功能可能不会出现在SQL2008标准中，等等。|1718518|在其他次要但经常被忽视的问题-+SQL+2008将只是64位，如果你购买新的硬件应该不是问题，但如果你计划使用现有的硬件……此外，如果您依赖于第三方驱动程序(例如oracle)，最好确保64位版本可用|1718519|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The Denver SQL Server Users group has had some really good presentations over the last couple of months on the new features in SQL 2008 including one from Paul Nielsen just last week shortly after he got back from "Jump Start" up in Redmond (if I remember the name of the event correctly).

A couple of caveats on all of the "new features" for SQL 2008, the triage to determine which features will be in the various editions is still in progress. Many/most of the new/very cool features like data compression, partitioned indexes, policies, etc. are only going to be in the enterprise edition. Unless you're planning on running enterprise edition a lot of the features that are in the CTP's will probably not be in SQL 2008 standard, etc.

On other minor but often overlooked issue - SQL 2008 will only be 64-bit, if you're buying new hardware shouldn't be an issue but if you're planning on using existing hardware... also, if you've got dependencies on third party drivers (e.g. oracle) best be sure that a 64-bit version is available/works

What are the key differences between Microsoft's SQL Server 2005 and SQL Server 2008? 

Are there any compelling reasons for upgrading (any edition, as I have a customer with multiple editions)? Or is there a website with either a chart or bullet point comparison of the two servers?

Also, is there anything noteworthy in the <a href="http://en.wikipedia.org/wiki/SQL_Server_Express" rel="noreferrer">Express</a> editions of either version?

Advantages of SQL Server 2008 over SQL Server 2005?

SQL Server

服务器

Microsoft的SQL Server 2005和SQL Server 2008之间的主要区别是什么？是否有任何令人信服的升级理由(任何版本，因为我有一个拥有多个版本的客户)？或者，是否有网站提供两台服务器的图表或项目符号比较？另外，在这两个版本的版本中有什么值得注意的地方吗？

问SQL Server 2008相对于SQL Server 2005的优势是什么？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SQL Server 2008相对于SQL Server 2005的优势是什么？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SQL Server 2008相对于SQL Server 2005的优势是什么？
EN