Editing Adaptive Server Enterprise (section)

==History==
Bob Epstein left [[Britton Lee, Inc.]] to help found [[Sybase]] and carried a lot of the ideas from the hardware database with him, reasoning that standard hardware such as Intel, Motorola and Sun 32 and 64 bit processors running database software could advance much more rapidly than specialist hardware. 
Originally developed for [[Unix]] operating system platforms in 1987, [[Sybase|Sybase Corporation]]'s primary [[relational database management system]] product was initially marketed under the name Sybase SQL Server.<ref name="DHH">{{cite book|last=Litchfield|first=David|title=The Database Hacker's Handbook: Defending Database Servers|url=https://books.google.com/books?id=CgQ8PLzCgcQC&q=Adaptive+Server+Enterprise+Sybase&pg=PA196|year=2005|publisher=Hungry Minds|isbn=8126506156|page=196}}</ref><ref>{{cite book|last1=Gunderloy|first1=Mike|last2=Sneath |first2=Tim|title=SQL Server's Developer's Guide to OLAP with Analysis Services|url=https://books.google.com/books?id=N36KgT-PApkC&q=origins+of+SQL+Server&pg=PA26|year=2001|publisher=SYBEX|isbn=0782153178|page=26}}</ref> [[Microsoft]]'s [[Bill Gates]] praised it as the world's best SQL [[database engine]];<ref name="mace19880118">{{Cite magazine |last=Mace |first=Scott |date=18 January 1988 |title= Ashton-Tate, Microsoft Join Forces To Introduce SQL Database Server|url=https://books.google.com/books?id=Dz8EAAAAMBAJ&pg=PA1#v=onepage&q&f=false |access-date=2025-05-25 |magazine=[[InfoWorld]] |pages=1,8 |volume=10 |issue=3}}</ref> in 1988, SQL Server for [[OS/2]] was co-developed for the PC by Sybase, Microsoft, and [[Ashton-Tate]].<ref>{{cite book|last1=Harris|first1=Scott|last2=Preston |first2=Curtis |title=Backup & Recovery: Inexpensive Backup Solutions for Open Systems|url=https://books.google.com/books?id=M9mbAgAAQBAJ&q=origins+of+SQL+Server+Sybase&pg=PA562|year=2007|publisher=O'Reilly|isbn=978-0596102463|page=562}}</ref>  Ashton-Tate divested its interest and Microsoft became the lead partner after porting SQL Server to [[Windows NT]].  Microsoft and Sybase sold and supported the product through version 4.2.1.

The key feature that made SQL Server attractive from the start was its high performance due to shared log writes, clustered indexes and a small [[memory footprint]] per user. As a result of these and other design features it performed well "out of the box".

Sybase released SQL Server 4.2 in 1992.  This release included [[internationalization and localization]] and support for [[symmetric multiprocessing]] systems.

In 1993, the co-development licensing agreement between Microsoft and Sybase ended, and the companies parted ways after an amicable solution was reached. Sybase wanted to develop on the Intel Unix platform and Microsoft wanted Windows specific solutions. As part of the agreement Sybase released the System 10 codeline to Microsoft and Microsoft gave up exclusive rights to Intel platforms. Both continuing to independently develop their respective versions of SQL Server. Sybase released Sybase SQL Server 10.0, which was part of the System 10 product family, which also included Back-up Server ( a very high performance parallel backup process), Replication Server ( to provide replicate sites), Navigation Server ( a shared nothing parallel server), Open Client/Server APIs, SQL Monitor, SA Companion and OmniSQL Gateway. Microsoft continued on with [[Microsoft SQL Server]].

Sybase provides native low-level programming interfaces to its database server which uses a protocol called [[Tabular Data Stream]]. Prior to version 10, DBLIB (DataBase LIBrary) was used. Version 10 and onwards uses CTLIB (ClienT LIBrary).

In 1995, Sybase released SQL Server 11.0.
Starting with version 11.5 released in 1996, Sybase moved to differentiate its product from [[Microsoft SQL Server]] by renaming it to Adaptive Server Enterprise.<ref name="DHH"/>
Sybase 11.5 added Asynchronous prefetch, case expression in sql, the optimizer can use a descending index to avoid the need for a worktable and a sort.
The Logical Process Manager was added to allow prioritization by assigning execution attributes and engine affinity.

In 1998, ASE 11.9.2 was rolled out with support for data pages locking, data rows (row-level locking), distributed joins and improved [[Symmetric multiprocessing|SMP]] performance. Indexes could now be 
created in descending order on a column, readpast concurrency option and repeatable read transaction isolation were added. A lock timeout option and task-to-engine affinity were added, 
query optimization is now delayed until a cursor is opened and the values of the variables are known.

In 1999, ASE 12.0 was released, providing support for [[Java (programming language)|Java]], high availability and distributed transaction management. Merge joins were added, previous all joins were nested loop joins. In addition, cache partitions were added to improve performance.

In 2001, ASE 12.5 was released, providing features such as dynamic memory allocation, an [[EJB]] container, support for [[XML]], [[Secure Sockets Layer]] (SSL) and [[LDAP]]. Also added was compressed backups, unichar [[UTF-16]] support and multiple logical page sizes 2K, 4K, 8K, or 16K.

In 2005, Sybase released ASE 15.0. It included support for partitioning table rows in a database across individual disk devices, and "virtual columns" which are computed only when required. In ASE 15.0, many parameters that had been static (which required server reboot for the changes to take place) were made dynamic (changes take effect immediately). This improved performance and reduced downtime. For example, one parameter that was made dynamic was the "tape retention in days" (the number of days that the backup is kept on the tape media without overwriting the existing contents in the production environment).

On January 27, 2010, Sybase released ASE 15.5. It included support for in-memory and relaxed-durability databases, distributed transaction management in the shared-disk cluster, faster compression for backups as well as Backup Server Support for the IBM Tivoli Storage Manager. Deferred name resolution for user-defined stored procedures, FIPS 140-2 login password encryption, incremental data transfer, bigdatetime and bigtime datatypes and tempdb groups were also added.

In July 2010, Sybase became a wholly owned subsidiary of [[SAP SE|SAP America]].<ref>[http://www.prnewswire.com/news-releases/sap-completes-acquisition-of-sybase-inc-99612339.html Press release of Sybase & SAP merger.]</ref> On September 13, 2011, Sybase released ASE 15.7 at [[Techwave]].<ref>{{cite web |url=https://techwave.at/cloud-produkte/ |title=Cloud Support |website=Retrieved 14 January 2022.}}</ref> It included support for: New Security features - Application Functionality Configuration Groups, a new threaded kernel, compression for large object (LOB) and regular data, End-to-End CIS Kerberos Authentication, Dual Control of Encryption Keys and Unattended Startup and extension for securing logins, roles, and password management, Login Profiles, ALTER... modify owner, External Passwords and Hidden Text, Abstract Plans in Cached Statements, Shrink Log Space, In-Row Off-Row LOB, using Large Object text, unitext, and image Datatypes in Stored Procedures, Using LOB Locators in Transact-SQL Statements, select for update to exclusively lock rows for subsequent updates within the same transaction, and for update-able cursors, Non-materialized, Non-null Columns with a default value, Fully Recoverable DDL (select into, alter table commands that require data movement, reorg rebuild), merge command, Expanded Variable-Length Rows, Allowing Unicode Noncharacters.

In April 2014, SAP released ASE 16. It included support for partition locking, CIS Support for HANA, Relaxed Query Limits, Query Plan Optimization with Star Joins, Dynamic Thread Assignment, Sort and Hash Join Operator improvements, Full-Text Auditing, Auditing for Authorization Checks Inside Stored Procedures, create or replace functionality, Query Plan and Execution Statistics in HTML, Index Compression, Full Database Encryption, Locking, Run-time locking, Metadata and Latch enhancements, Multiple Trigger support, Residual Data Removal, Configuration History Tracking, CRC checks for dump database and the ability to calculate the transaction log growth rate for a specified time period.
<!-- ===Version numbering===
The version number was bumped to [[15 (number)|15]] from 12 because{{citation needed|date=December 2011}} [[13 (number)|13]] is considered unlucky in [[Europe]], the [[United States]] and other [[Western world|Western]] countries, and [[14 (number)|14]] is considered unlucky in [[China]]. -->