34,590
社区成员
发帖
与我相关
我的任务
分享SQL Server下一版Yukon会跨平台吗？
据说SQL Server下一版Yukon将全面支持.NET,估计一定很精彩，但是微软看来不会仅仅停留在WINDOWS平台，目前我在做一个项目的选型，就算因为WINDOWS被认为是低端不稳定产品，而在别的平台下有用不了SQL SERVER，所以忍痛割爱只好选择别的数据库。。。
谈谈你对Yukon的了解和认识，欢迎大家踊跃发言！
谈谈你对Yukon的了解和认识，欢迎大家踊跃发言！
...全文
请发表友善的回复…
发表回复
OpenVMS 2003-04-05
- 打赏
- 举报
UP
OpenVMS 2003-04-04
- 打赏
- 举报
高端用户一般还不用SQL SERVER，据说ORACLE，DB2，SQL SERVER三分天下
SQL SERVER YUKON（2003）的权威介绍见
http://www.microsoft.com/sql/evaluation/yukon.asp
主要内容：
有32和64位版本，打算在今年微软开发者大会后发布
在备份、恢复、复制功能有所增强
通过XML、WEB service增强数据的互操作性
全新的管理工具方便日常数据库管理和性能调试，改进了SQL PROFILER等工具
和Visual Studio.NET集成，如任务向导和职能感应功能（.NET beta2 IDE确实很职能）
可用一个工具同时进行TSQL、XML、MDX的开发
增强XML和用户自定于数据类型
支持HTTP、XML、Simple Object Access Protocol (SOAP), XQuery, and XML Schema Definition (XSD)，可与任何平台进行通讯
另外在OLAP、数据挖掘方面也有改进。
希望现在大家遇到的BUG能彻底削除就已经不错了~~~~~~~~~~~
SQL SERVER YUKON（2003）的权威介绍见
http://www.microsoft.com/sql/evaluation/yukon.asp
主要内容：
有32和64位版本，打算在今年微软开发者大会后发布
在备份、恢复、复制功能有所增强
通过XML、WEB service增强数据的互操作性
全新的管理工具方便日常数据库管理和性能调试，改进了SQL PROFILER等工具
和Visual Studio.NET集成，如任务向导和职能感应功能（.NET beta2 IDE确实很职能）
可用一个工具同时进行TSQL、XML、MDX的开发
增强XML和用户自定于数据类型
支持HTTP、XML、Simple Object Access Protocol (SOAP), XQuery, and XML Schema Definition (XSD)，可与任何平台进行通讯
另外在OLAP、数据挖掘方面也有改进。
希望现在大家遇到的BUG能彻底削除就已经不错了~~~~~~~~~~~
愉快的登山者 2003-04-03
- 打赏
- 举报
不会跨平台的，微软还要推自己的操作系统，不能用自己的产品帮助他人竞争。
yoki 2003-04-03
- 打赏
- 举报
人家就靠windows吃饭呢
CoolAbu 2003-04-03
- 打赏
- 举报
听课
OpenVMS 2003-04-03
- 打赏
- 举报
谢谢各位积极参与,楼上的有一定道理,因为SQL SERVER不少功能依赖于WINDOWS,不是独立产品.
shengyh 2003-04-03
- 打赏
- 举报
现在90％以上的用户我想还是在windows平台下进行！接分！！！！！！
leimin 2003-04-03
- 打赏
- 举报
Preparing for Yukon
Yukon is still a ways off, but it's not too early to start preparing for the dramatic changes the new SQL Server release will bring—especially those associated with Microsoft's .NET Common Language Runtime (CLR). SQL Server 7.0 transformed SQL Server's underlying database-engine architecture, but the way that DBAs manage the server remained essentially the same. You still use Enterprise Manager for multiserver management and T-SQL to create and update databases and their objects. Although Yukon features the same underlying architecture, the release has big changes in store for DBAs.
With Yukon's CLR integration, you'll be able to use languages other than T-SQL to create database objects and retrieve and update data. T-SQL isn't going away, and some DBAs might try to simply ignore the new .NET languages they find in their toolbox. However, learning about the .NET Framework and the CLR will help you support the third-party applications that are certain to adopt these language enhancements and will help you understand where the enhancements can improve your own application and database performance.
You can start preparing for Yukon today by learning about the .NET Framework, its ADO.NET data-access object layer, and at least one of the .NET languages. The big language question is when should you use these new languages as opposed to T-SQL? To determine the best places to use a .NET language, you first need to investigate the characteristics of each alternative. For example, T-SQL is a powerful procedural language well suited to data retrieval and manipulation. However, T-SQL is weak in the areas of structure, flow control, and reusability, so applying T-SQL to problems that require complex logic is difficult. Object-oriented .NET languages such as Visual Basic .NET and C# provide adequate data-manipulation capabilities by using ADO.NET to execute SQL statements. But their strong points are structure and flow control, making them well suited for solutions that require complex logic. So, in general, T-SQL is better suited to raw data retrieval and modification, and the .NET languages are better suited to enforcing business rules.
The next step in preparing to take advantage of Yukon's language enhancements is to determine whether your existing stored procedures, triggers, and user-defined functions (UDFs) are primarily data-oriented or whether they implement business logic. If your procedures contain complex logic, you can begin expressing that logic in pseudo code, which will act as a guide to writing more-effective CLR stored procedures later. Or if you have Visual Studio .NET and are familiar with a .NET language, you could even begin rewriting the procedures in that language. You should also review your database design to see where your applications' data-access objects reside. With SQL Server's CLR integration, you'll be able to move your data-access objects from the data tier to the server, which could significantly boost your applications' performance.
You might not be able to roll out these procedures for a while. But time has a way of creeping up on you, and Yukon will be here before you know it. Nothing would put you in a better position to hit the ground running with the next release of SQL Server than to evaluate when and where to use the new CLR languages in your environment
Yukon is still a ways off, but it's not too early to start preparing for the dramatic changes the new SQL Server release will bring—especially those associated with Microsoft's .NET Common Language Runtime (CLR). SQL Server 7.0 transformed SQL Server's underlying database-engine architecture, but the way that DBAs manage the server remained essentially the same. You still use Enterprise Manager for multiserver management and T-SQL to create and update databases and their objects. Although Yukon features the same underlying architecture, the release has big changes in store for DBAs.
With Yukon's CLR integration, you'll be able to use languages other than T-SQL to create database objects and retrieve and update data. T-SQL isn't going away, and some DBAs might try to simply ignore the new .NET languages they find in their toolbox. However, learning about the .NET Framework and the CLR will help you support the third-party applications that are certain to adopt these language enhancements and will help you understand where the enhancements can improve your own application and database performance.
You can start preparing for Yukon today by learning about the .NET Framework, its ADO.NET data-access object layer, and at least one of the .NET languages. The big language question is when should you use these new languages as opposed to T-SQL? To determine the best places to use a .NET language, you first need to investigate the characteristics of each alternative. For example, T-SQL is a powerful procedural language well suited to data retrieval and manipulation. However, T-SQL is weak in the areas of structure, flow control, and reusability, so applying T-SQL to problems that require complex logic is difficult. Object-oriented .NET languages such as Visual Basic .NET and C# provide adequate data-manipulation capabilities by using ADO.NET to execute SQL statements. But their strong points are structure and flow control, making them well suited for solutions that require complex logic. So, in general, T-SQL is better suited to raw data retrieval and modification, and the .NET languages are better suited to enforcing business rules.
The next step in preparing to take advantage of Yukon's language enhancements is to determine whether your existing stored procedures, triggers, and user-defined functions (UDFs) are primarily data-oriented or whether they implement business logic. If your procedures contain complex logic, you can begin expressing that logic in pseudo code, which will act as a guide to writing more-effective CLR stored procedures later. Or if you have Visual Studio .NET and are familiar with a .NET language, you could even begin rewriting the procedures in that language. You should also review your database design to see where your applications' data-access objects reside. With SQL Server's CLR integration, you'll be able to move your data-access objects from the data tier to the server, which could significantly boost your applications' performance.
You might not be able to roll out these procedures for a while. But time has a way of creeping up on you, and Yukon will be here before you know it. Nothing would put you in a better position to hit the ground running with the next release of SQL Server than to evaluate when and where to use the new CLR languages in your environment
OpenVMS 2003-04-03
- 打赏
- 举报
微软这方面资料太少,看来让大家失望了
caiyunxia 2003-04-03
- 打赏
- 举报
学习
lynx800602 2003-04-03
- 打赏
- 举报
来看热闹了！！：）
CrazyFor 2003-04-03
- 打赏
- 举报
来学习了！！：）
stwx 2003-04-03
- 打赏
- 举报
64位的 SQL2000出来了没有! 配上 双至强 64 位 CPU一定很快吧
milchcow 2003-04-03
- 打赏
- 举报
MS的产品没有跨平台的,要是SQL SERVER跨平台了,那跟SQL SERVER相关的服务器产品也要跨平台了.
昵称被占用了 2003-04-02
- 打赏
- 举报
听课
xpilot 2003-04-02
- 打赏
- 举报
4月份只是发布vs.net 2003 ,今年中发布64位版sql2000,最早明年才会发布Yukon,等的花儿也谢了.....
cy_soft 2003-04-02
- 打赏
- 举报
不可能跨平台！！！
happydreamer 2003-04-02
- 打赏
- 举报
不是说4月份发布么
xpilot 2003-04-02
- 打赏
- 举报
可惜现在连个预览版本都找不到，ms也保密的太严了，只有某些高级用户才可以试用！
据说Yukon要实现的一个功能是用.net 语言写外部存储过程，现在只能用c或c++来写，而且语法十分烦杂，希望用C#写的时候早日到来.没有非常强大的外部存储过程，的确是数据库的遗憾！
据说Yukon要实现的一个功能是用.net 语言写外部存储过程，现在只能用c或c++来写，而且语法十分烦杂，希望用C#写的时候早日到来.没有非常强大的外部存储过程，的确是数据库的遗憾！
zhang2544669 2003-04-02
- 打赏
- 举报
真希望能。
加载更多回复（3）
