PRN: SQL Server 2012 Licensing Rules Explained
SQL Server 2012 Licensing Rules Explained [15-March-2012] KIRKLAND, Washington, March 15, 2012 /PRNewswire/ -- Â Independent Microsoft licensing experts dissect changes SQL Server 2012, the newest version of Microsoft's database server application, just shipped.
SQL Server 2012 Licensing Rules Explained
KIRKLAND, Washington, March 15, 2012 /PRNewswire/ --
Independent Microsoft licensing experts dissect changes
SQL Server 2012, the newest version of Microsoft's database server application, just shipped. The new version introduces a variety of highly compelling enhancements in areas such as disaster recovery, business intelligence, and database application management. It also introduces packaging, pricing and licensing changes that will have a material impact on the decisions of IT planners and procurement professionals, including:
Directions on Microsoft licensing analysts Rob Horwitz and Wes Miller will explain the new pricing, packaging and licensing rules for SQL Server 2012 and answer audience questions during a live webinar at 10:00 a.m. PDT on March 22nd, 2012.Â
Those interested in participating in the SQL Server Licensing Webinar can register at: http://www.DirectionsOnMicrosoft.com/SQL_Server_Licensing
"It's hard to understate the cost implications and other effects of these changes," says Directions on Microsoft founder and licensing authority Rob Horwitz.Â "It will even impact what hardware customers buy to run SQL Server and sometimes even when the hardware is purchased."
According to Horwitz, "the transition issues for existing SQL Server customers are especially tricky and are largely determined by how the customer licensed SQL Server in the past." Whether a customer chose to buy earlier versions of SQL Server under a per-processor licensing model or under a server + Client Access Licenses (CALs) model has significant implications. Also key is whether or not a customer has licenses covered by Software Assurance (SA), and if so, when the SA term ends as well as whether SA was purchased through Select programs or through an Enterprise Agreement (EA). Depending on customer circumstances, some options for reducing costs and minimizing compliance exposure are very time sensitive.
About Directions on Microsoft