by Renee L
In his article “Microsoft’s SQL Server 2012 Has Muscle, but Database Battle is Fierce,” Mark Fontecchio examines the new features of Microsoft’s new version of the SQL Server and what it has to offer. Some of the great features added to the SQL Server 2012 are the AlwaysOn, which allows a set of databases to fail over as a single unit, xVelocity, a feature that speeds up querying, and Power View and PowerPivot, which provides self-service business intelligence. However, Fontecchio argues that, even though Microsoft’s SQL Server 2012 is probably one of the best releases Microsoft has made, it may not be enough to overcome leading database systems, such as Oracle’s database and IBM’s DB2. Experts say that there are limitations to the new SQL Server. Such limitations are that it must be run on x86 servers with a Windows operating system and when using xVelocity, indexes cannot be updated, therefore, you must rebuild them whenever you want to add more data. In addition, companies do not just change database systems no matter how good the price is. It is hard to change databases and companies will not do so unless the system is really worth it. All in all, Microsoft customers will be happy with the new SQL Server and its added features, however, it may not make a big impact on enterprises.
The topic of this article relates to the physical database design process we learned this week during class. Microsoft SQL Server 2008 is the system that we will be using for our physical database design project and from there, we would be able to see and use some of the features that it offers.
This is the first time that I have ever used the Microsoft SQL Server for databases. I have only had experience with Microsoft Access, which I found very difficult to use. In Microsoft Access, it took me a while to learn how to run and create queries, and generate reports and charts. Now that I have access to the Microsoft SQL Server, I like the server better because of its advanced tools, rather than the Microsoft Access where it can only hold so much data.
Fontecchio, M. F. (2012). Microsoft’s sql server 2012 has muscle, but database battle is fierce.SearchSQLServer, Retrieved from http://searchsqlserver.techtarget.com/news/2240148706/Microsofts-SQL-Server-2012-has-muscle-but-database-battle-is-fierce