Reference:
- http://garsy.cntask.net/2010/05/07/sql-server-2008-r2-release/
- http://oreilly.com/catalog/wintrnssql/chapter/ch01.html
SQL Server, like many things related to SQL, is a story of diversity. At one time, both Sybase and Microsoft had virtually the same product. Today, the two products are growing increasingly divergent. In fact, Sybase now calls their implementation of the product Sybase Adaptive Server Enterprise. For purposes of simplicity, in this book we refer to both Microsoft and Sybase implementations as SQL Server.
Today, major differences in the two implementations are largely a result of their most popular operating system and hardware platforms. Sybase Adaptive Server Enterprise is deployable on many operating systems, including Windows NT and stalwart Unix platforms. Adaptive Server has many features that leverage Very Large Database (VLDB) and multithreading capabilities. Sybase carries the Transact-SQL language uniformly throughout their product line. So, you’re just as likely to see Transact-SQL programs on the powerful and mobile Sybase SQL Adaptive Server Anywhere (formerly known as SQL Anywhere) running on Windows 95 and Windows 98 computers. Going to the high end of the spectrum for online analytical processing (OLAP) and data warehouses, Sybase Adaptive Server IQ utilizes Transact-SQL for programmatic needs and, in fact, utilizes the same parser as Sybase Adaptive Server. Conversely, Microsoft has focused on ease of use and administration, as well as tightly integrating the product with other no-cost features like replication and alert forwarding. In any event, all of these database platforms provide their respective user groups with efficient and effective database management tools.
Today, there’s a good deal of discussion about encapsulating Java as the primary SQL programming extension for not only Sybase and Microsoft but also for competitors like Oracle. Even with this alternative looming in the distance, Transact-SQL will enjoy many years of active support and augmentation by the vendors. Even if you know or are learning Java, you’ll still have to know Transact-SQL to excel on either Sybase or Microsoft database platforms. Heck, the backward-compatibility issues alone are enough to ensure that Transact-SQL will have many, many more years of coding ahead.
But that’s the present and future. Maybe you want to know about how things got to be the way they are? By reading this section, you are actually making an admission that many programmers and analysts are loath to: history is interesting or perhaps even enjoyable. This is not actually a sign of weakness as some might attest. With tongue planted firmly in cheek, please read on. Table 1-1 shows the evolution of both Microsoft and Sybase’s versions of SQL Server
| Time | Event |
|---|---|
| 1987 | Microsoft and Sybase announce a technology and marketing partnership. Microsoft gets exclusive rights to market Sybase’s DataServer product on OS/2 and all Microsoft-developed operating systems. Sybase gets royalties and added credibility in the Unix and VMS markets. Sybase ships its first commercial DBMS product, called DataServer, for Sun workstations running Unix. |
| 1988 | Microsoft and Ashton-Tate announce a marketing partnership. Microsoft can’t put a dent in dBase’s tremendous market presence. Ashton-Tate wants access to Sybase’s powerful multiuser database management technology, which ships this year. Microsoft forms a three-way alliance. |
| 1989 | Ashton-Tate/Microsoft SQL Server Version 1.0 ships. |
| 1990 | Ashton-Tate dBase IV was floundering. Microsoft wanted to beef up its offerings for the new OS/2 LAN Manager product. Microsoft and Ashton-Tate quit the partnership. “Microsoft SQL Server” Version 1.1 ships by summer with support for Windows 3.0. |
| 1991 | A proliferation of Windows 3.0 front-end tools spurs the growth of Microsoft SQL Server. Later that year Microsoft and Sybase amend their contract to allow Microsoft to make actual bug fixes–all under Sybase supervision. IBM and Microsoft call off their OS/2 partnership with Microsoft to focus on Windows. Sybase surpasses $100 million in revenue and goes public on NASDAQ. |
| 1992 | Microsoft and Sybase SQL Server 4.2 ships. Microsoft diverts its attention away from OS/2 and into Windows NT. Microsoft SQL Server for Windows NT later ships its beta release while Sybase ships its much-vaunted System 10. |
| 1993 | Microsoft Windows NT 3.1 ships, closely followed by Microsoft SQL Server. By 1994, Sybase SQL Server System 10 and Microsoft SQL Server were competing unabashedly as the two formally ended their partnership. |
| 1995 | Microsoft SQL Server 6.0, a very significant release, ships in June. Sybase ships the highly lauded, technically potent Sybase SQL Server 11. Sybase and PowerSoft merge to form the seventh largest independent software house. |
| 1996 | Microsoft SQL Server 6.5 goes into production. Sybase Adaptive Server Enterprise 11.5 production ships. |
| 1997 | Microsoft SQL Server 7.0 beta ships. Sybase ships the production version of Adaptive Server Enterprise 11.5. |
| 1998 | Sybase Adaptive Server Anywhere 6.0 ships in the summer, while the Adaptive Server Enterprise 11.9.2 production release goes out the door in September. Microsoft SQL Server 7.0 ships release to manufacturing copy late in the year. |
It is an issue I must find more information about, thanks for the posting.
And where is the facebook like button ?
Just want to say your article is as astonishing. The clarity in your post is just cool and i can assume you’re an expert on this subject. Well with your permission allow me to grab your RSS feed to keep updated with forthcoming post. Thanks a million and please keep up the gratifying work. whm reseller | best reseller hosting |
Where exactly is the facebook like button ?
Hi Bert,
Thanks for your idea!And now, you may find them from each topic.
Thanks again.
Garsy
Good blogging!
Hi Aidan,I know that sql sverer 2005 has been added to all new windows hosting accounts as this was my main motivation for joining with register365. I checked before I joined by contacting your support centre and I was assured that sql sverer 2005 was available, and in fairness it is.My problem however is that it doesn’t work. I have been able to login and create a sql sverer 2005 database but I cannot connect to the database from asp.net applications hosted on your sverers. Furthermore, I couldn’t get this issue resolved by the support team and was told that it was a known issue but that your engineers could not provide any estimation of when the issue would be resolved. After several wasted days I eventually decided to sign up with digiweb and create a database on their sverers.When I then pointed my ASP.NET code (hosted with register365) at my new database (hosted by digiweb) I received the same error. It turns out (as far as I can see), that the issue is not with the SQL Server 2005 databases itself, but rather that the firewall or some port settings on register365 sverers block all access to any SQL Server 2005 database.Hence, why my original post stated that their was no SQL Server 2005 Environment available to your customers. Surely, you will agree that whether or not register365 offer customers access to Sql sverer 2005 the fact that they cannot develop applications that have a SQL sverer 2005 back end means that offering this service and advertising it as being available is a little mis-leading.I apologise for my rant, but I became a little frustrated as I wasted a lot of time trying to get my application set up on register365s environment and was disappointed as I had heard positive stories about register365 but in the end was left with no choice but to open a second hosting account with Digiweb.This is the error message that is displayed when my ASP.NET applications hosted by register365 trys to access a SQL Server 2005 database:An error has occurred while establishing a connection to the sverer. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 Could not open a connection to SQL Server)
This error msg you posted is very interest.
“An error has occurred while establishing a connection to the server.
(provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 5)
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 1326)”
I try to find a few similar solution for this issue:
SQL SERVER – FIX : ERROR : (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: )
another solution is from MSDN:
Named Pipes Provider, error: 40 – Could not open a connection to SQL Server
Enjoy it.
This is something I must do more research into, appreciate the post.