Mythbusters - "SQL Server is Sybase's product instead of Microsoft"
HTTPS: // www.cnblogs.com/xxxtech/archive/2011/12/30/2307859.html original author's translation actually sqlserver2008 start to sqlserver2017 biggest change should be embedded in-memory database and columnar storage and AI tools such as python but we basically have no company with his heart characteristics ..
by Euan Garden
All these years I've heard a lot of rumors about this version, the most interesting is the number to "Microsoft to buy late to confuse the Sybase code, but it is still Sybase SQL Server product."
First, let's look at history. In 1987, Microsoft and Sybase company launched a cooperation to jointly build and market products based on Sybase DataServer database management systems. Sybase SQL Server on the rights of Unix / minicomputer platform, and Microsoft SQL Server at the right time on the nascent OS / 2 platform and any platform developed by Microsoft's.
That period, Ashton Tate's dBase in the "PC" database system (non-mainframe / minicomputer / Unix) are in the leading position (my first database application that is used on DOS 3.3 platform dBaseIII +). In order to make better use of existing large and Ashton Tate dBase provide true client-server, Microsoft and Ashton Tate released Ashton Tate / Microsoft SQL Server (Sybase later their products on UNIX and VMS platforms help in Sybase rename the Sybase SQL Server), which later became Sybase DataServer name on the OS / 2 platform.
Ashton Tate / Microsoft SQL Server version first published in 1989. Initially, dBase IV plans to provide front-end development tool for SQL Server (based on previous cooperation), but in dBase IV delayed release of the year led to a miscarriage of the plan. So, Microsoft and Ashton Tate broke up the partnership, the product has also been named as a Microsoft SQL Server (now there are still some members of the development team was very proud of the box has a printed Ashton-Tate / Microsoft SQL Server's).
Since then, Microsoft continues to improve SQL Server, added support for the Windows platform in 1990 released SQL Server 1.1 in. However, most of the work still to complete Sybase, Microsoft is only responsible for testing, project management and some minor development. By the year 1991, in order to correct defects in the product, Microsoft team was able to read and then changed to modify the code SQL Server. Cooperation on the first version of a true sense of the 1992 release of version 4.2 of its OS / 2 versions of the code and Sybase 4.0 code phase synchronization. It is noteworthy that for the first time Microsoft's code is the same as Sybase code for that version.
Then the situation began to heat up, working in 32-bit version of Microsoft SQL Server, Sybase launched a research and development on the System 10 platforms. This time, OS / 2 platform shows a lack of competitiveness, while Microsoft has completed the beta version of Windows NT and only 32-bit version. So SQL Server team decided to build a port on the NT platform in a stable version of the code on the basis of 4.2, and Sybase System 10 platform continues to develop. Now use the "port" is the word has a less appropriate. NT platform offers many opportunities for the characteristics of the product using the operating system, the key is the operating system provides the ability to support running on SMP systems, rather than having to write the code in the database. The team did, led on the SQL Server version 4.2 and NT on the OS / 2 platform has been very different (side note: sqlnt had been developed for internal mail accounts to communicate, the account still exists today and We have a development team, support team members, documentation and courseware team).
So far, Microsoft and Sybase's cooperation began to lose its value. Sybase wants to keep the neutrality of the platform, and Microsoft hopes were invested in the Windows NT platform. In addition, subject to the agreement, Microsoft must be able to add new features for the Sybase SQL Server after approval. Their collaboration in 1994 collapse, Sybase was first to allow their products on OS / 2 and Windows platforms release, Microsoft Products can be brought to the direction you want. In just 18 months, Microsoft NT platform on the basis of the original SQL Server code on the released SQL Server 6.0 and 6.5. These versions rewrite existing code and adding new code. It was also during this time, Microsoft has the right and the success of the code SQL Server, and make it significantly different from the original OS / 2 platform version 4.2 of Sybase code.
In this process of change, Microsoft has decided to expand the data management front. This means they have a lot of work to do, including the establishment of a more powerful team. Microsoft hired a number of database best in the industry and the most experienced expert (Hal Berenson from the DEC, Peter Spiro, David Campbell et al., IBM's James Hamilton, Lubor Kollar et al., Oracle's Bill Baker, Pedro Celis, and Tandem the Pat Hellan), and for the best researchers equipped them (Jim Gray, Phil Bernstein et al.) and the world's most intelligent database of professional master's and doctorate from. And they had the soul (as Ron Soukup) team as well as some of Microsoft's internal staff in a short time established a great and dedicated team. Some of the team is committed to SQL Server 6.0 / 6.5, and most people are code-named Sphinx that is developed SQL Server 7.0.
Sphinx goal is clear, to establish a new set of standards to simplify the complete data management. This means that in the next few years to build a scalable platform, and to learn from each previous version of SQL Server and other database platforms. For this purpose must be rewritten database engine, new query processor, the new storage engine and a new set of data access API (OLE DB and ADO, eventually into the dblib).
Although SQL Server relational database management system known Microsoft wanted a solution in SQL Server 7.0 provides a complete data. Added support for online analytical processing (this part of the code from the acquisition of Israel "Plato" Company) by OLAP services through DTS integrated data extraction, transformation, and loading (this part of the code by the internal Starfighter / Tools Team development).
SQL Server 7.0 RTM version released in November 1998 (the week I just interviewed in Redmond, remember the main campus, Building 1, Building 3, and very lively) and released the official version in January 1999. Although I am a little biased, but I believe that the work done by Microsoft to be more than I listed above. So can you say Microsoft SQL Server is Sybase's product? The main components of the newly added is not rewritten, so Microsoft SQL Server and Sybase SQL Server does not have any relationship.
Apparently SQL Server journey does not stop at version 7.0. Followed by the August 2000 release of SQL Server 2000. The main work includes a multi-instance and cluster implementations (All code is Microsoft's self-produced), data mining (from Microsoft Research conducted earlier research project), SQLXML (MDAC from the team and a network interface the aid project).
Before SQL Server 2005, new features of the most influential SQL Server 2000 Reporting Services is offered. Code of Reporting Services 2000 SQL Server Microsoft entirely self-produced. Reporting Services development team from the original Repository / Meta Data Services team, some English query team members and a group of new components.
SQL Server 2005 major new features and code worth a few blog to introduce separately, but I would like to emphasize SQLCLR (from a long-term strategy for integrated projects), XML support (we have investigated the best way to store XML in using a dedicated database or XML will be integrated into XML in SQL Server chose the latter. it takes a lot of changes in quadratic programming language and to support XQuery), Service Broker (in Dave Campbell and surveys in Israel MSMQ team after messaging / queuing / SOA, we decided to integrate this aid project), integration Services (from bits and pieces of code from the original DTS team and a few from C ++, hardware, AS and COM + team of people putting together a new team, plus a small-scale acquisitions to build environmental design and execution), Report Builder (based on an acquisition concept and architecture, but the code is new).
Dave Campbell had told him one day over 10-year career SQL Server, there are still some members of time in the team longer than him, but the SQL Server team (MDAC, System.Data, System.XML and WinFS) all 1,000 people , a few people have seen his party is not a Microsoft employee wrote the code.
Conclusion: The rumors are ended!
See original: http://blogs.msdn.com/b/euanga/archive/2006/01/19/514479.aspx
Follow-up: http://blogs.msdn.com/b/euanga/archive/2006/05/23/597677.aspx
The first attempt to translate, turn relatively stiff, like him to teach.
by Euan Garden
All these years I've heard a lot of rumors about this version, the most interesting is the number to "Microsoft to buy late to confuse the Sybase code, but it is still Sybase SQL Server product."
First, let's look at history. In 1987, Microsoft and Sybase company launched a cooperation to jointly build and market products based on Sybase DataServer database management systems. Sybase SQL Server on the rights of Unix / minicomputer platform, and Microsoft SQL Server at the right time on the nascent OS / 2 platform and any platform developed by Microsoft's.
That period, Ashton Tate's dBase in the "PC" database system (non-mainframe / minicomputer / Unix) are in the leading position (my first database application that is used on DOS 3.3 platform dBaseIII +). In order to make better use of existing large and Ashton Tate dBase provide true client-server, Microsoft and Ashton Tate released Ashton Tate / Microsoft SQL Server (Sybase later their products on UNIX and VMS platforms help in Sybase rename the Sybase SQL Server), which later became Sybase DataServer name on the OS / 2 platform.
Ashton Tate / Microsoft SQL Server version first published in 1989. Initially, dBase IV plans to provide front-end development tool for SQL Server (based on previous cooperation), but in dBase IV delayed release of the year led to a miscarriage of the plan. So, Microsoft and Ashton Tate broke up the partnership, the product has also been named as a Microsoft SQL Server (now there are still some members of the development team was very proud of the box has a printed Ashton-Tate / Microsoft SQL Server's).
Since then, Microsoft continues to improve SQL Server, added support for the Windows platform in 1990 released SQL Server 1.1 in. However, most of the work still to complete Sybase, Microsoft is only responsible for testing, project management and some minor development. By the year 1991, in order to correct defects in the product, Microsoft team was able to read and then changed to modify the code SQL Server. Cooperation on the first version of a true sense of the 1992 release of version 4.2 of its OS / 2 versions of the code and Sybase 4.0 code phase synchronization. It is noteworthy that for the first time Microsoft's code is the same as Sybase code for that version.
Then the situation began to heat up, working in 32-bit version of Microsoft SQL Server, Sybase launched a research and development on the System 10 platforms. This time, OS / 2 platform shows a lack of competitiveness, while Microsoft has completed the beta version of Windows NT and only 32-bit version. So SQL Server team decided to build a port on the NT platform in a stable version of the code on the basis of 4.2, and Sybase System 10 platform continues to develop. Now use the "port" is the word has a less appropriate. NT platform offers many opportunities for the characteristics of the product using the operating system, the key is the operating system provides the ability to support running on SMP systems, rather than having to write the code in the database. The team did, led on the SQL Server version 4.2 and NT on the OS / 2 platform has been very different (side note: sqlnt had been developed for internal mail accounts to communicate, the account still exists today and We have a development team, support team members, documentation and courseware team).
So far, Microsoft and Sybase's cooperation began to lose its value. Sybase wants to keep the neutrality of the platform, and Microsoft hopes were invested in the Windows NT platform. In addition, subject to the agreement, Microsoft must be able to add new features for the Sybase SQL Server after approval. Their collaboration in 1994 collapse, Sybase was first to allow their products on OS / 2 and Windows platforms release, Microsoft Products can be brought to the direction you want. In just 18 months, Microsoft NT platform on the basis of the original SQL Server code on the released SQL Server 6.0 and 6.5. These versions rewrite existing code and adding new code. It was also during this time, Microsoft has the right and the success of the code SQL Server, and make it significantly different from the original OS / 2 platform version 4.2 of Sybase code.
In this process of change, Microsoft has decided to expand the data management front. This means they have a lot of work to do, including the establishment of a more powerful team. Microsoft hired a number of database best in the industry and the most experienced expert (Hal Berenson from the DEC, Peter Spiro, David Campbell et al., IBM's James Hamilton, Lubor Kollar et al., Oracle's Bill Baker, Pedro Celis, and Tandem the Pat Hellan), and for the best researchers equipped them (Jim Gray, Phil Bernstein et al.) and the world's most intelligent database of professional master's and doctorate from. And they had the soul (as Ron Soukup) team as well as some of Microsoft's internal staff in a short time established a great and dedicated team. Some of the team is committed to SQL Server 6.0 / 6.5, and most people are code-named Sphinx that is developed SQL Server 7.0.
Sphinx goal is clear, to establish a new set of standards to simplify the complete data management. This means that in the next few years to build a scalable platform, and to learn from each previous version of SQL Server and other database platforms. For this purpose must be rewritten database engine, new query processor, the new storage engine and a new set of data access API (OLE DB and ADO, eventually into the dblib).
Although SQL Server relational database management system known Microsoft wanted a solution in SQL Server 7.0 provides a complete data. Added support for online analytical processing (this part of the code from the acquisition of Israel "Plato" Company) by OLAP services through DTS integrated data extraction, transformation, and loading (this part of the code by the internal Starfighter / Tools Team development).
SQL Server 7.0 RTM version released in November 1998 (the week I just interviewed in Redmond, remember the main campus, Building 1, Building 3, and very lively) and released the official version in January 1999. Although I am a little biased, but I believe that the work done by Microsoft to be more than I listed above. So can you say Microsoft SQL Server is Sybase's product? The main components of the newly added is not rewritten, so Microsoft SQL Server and Sybase SQL Server does not have any relationship.
Apparently SQL Server journey does not stop at version 7.0. Followed by the August 2000 release of SQL Server 2000. The main work includes a multi-instance and cluster implementations (All code is Microsoft's self-produced), data mining (from Microsoft Research conducted earlier research project), SQLXML (MDAC from the team and a network interface the aid project).
Before SQL Server 2005, new features of the most influential SQL Server 2000 Reporting Services is offered. Code of Reporting Services 2000 SQL Server Microsoft entirely self-produced. Reporting Services development team from the original Repository / Meta Data Services team, some English query team members and a group of new components.
SQL Server 2005 major new features and code worth a few blog to introduce separately, but I would like to emphasize SQLCLR (from a long-term strategy for integrated projects), XML support (we have investigated the best way to store XML in using a dedicated database or XML will be integrated into XML in SQL Server chose the latter. it takes a lot of changes in quadratic programming language and to support XQuery), Service Broker (in Dave Campbell and surveys in Israel MSMQ team after messaging / queuing / SOA, we decided to integrate this aid project), integration Services (from bits and pieces of code from the original DTS team and a few from C ++, hardware, AS and COM + team of people putting together a new team, plus a small-scale acquisitions to build environmental design and execution), Report Builder (based on an acquisition concept and architecture, but the code is new).
Dave Campbell had told him one day over 10-year career SQL Server, there are still some members of time in the team longer than him, but the SQL Server team (MDAC, System.Data, System.XML and WinFS) all 1,000 people , a few people have seen his party is not a Microsoft employee wrote the code.
Conclusion: The rumors are ended!
See original: http://blogs.msdn.com/b/euanga/archive/2006/01/19/514479.aspx
Follow-up: http://blogs.msdn.com/b/euanga/archive/2006/05/23/597677.aspx
The first attempt to translate, turn relatively stiff, like him to teach.