Are You remember "Sliders"? In my opinion Licensing World is similar to this series. How many time You tried to understand licensing? How many times You heard different opinions about same question? I'm sure, that You know what is CPU, CORE, SOCKET. Are You familiar with Processor / User / Device? And CAL / SAL/ SA too? Are You use SPLA program or just OEM or MOLP? Physical Instance, Virtual Instance, 90 Days, EULA, SPUR, LAR, Multiplexing, 5 Dollars (not 5 Cents)... It's not all the possibilities, if we are talking about licenses. Let's talk about it, from the Licensing Point of View
Software architecture to analyze licensing needs for pcms- pegasus cargo ma...Shahzad
The document discusses licensing needs for the Pegasus Cargo Management System (PCMS) software. It provides information on SQL Server editions and licensing, including definitions of the different editions (e.g. Datacenter, Enterprise, Standard), their features and limitations. It also includes comparison charts summarizing the scalability, management tools, programmability, security, and reporting capabilities of each edition. The goal is to help determine the appropriate SQL Server edition licensing required to support the PCMS software.
Presentation by Bruce Campbell of Microsoft
Learn about a new capability in SQL Server 2008 R2, Parallel Data Warehouse, formerly known as Project Madison.
NZSPC 2013 - Ultimate SharePoint Infrastructure Best Practices SessionMichael Noel
Michael Noel is the author of 19 technical books on Microsoft technologies that have sold over 300,000 copies. He is a partner at Convergent Computing, an infrastructure and security consulting firm. The document provides hardware and software requirements for SharePoint 2013 environments, including recommended memory, processors, and editions of Windows Server and SQL Server. It also summarizes new features in SharePoint 2013 like the distributed cache service, request management, and claims-based authentication.
Effective Usage of SQL Server 2005 Database Mirroringwebhostingguy
The document discusses SQL Server 2005 database mirroring, including concepts like principal and mirror databases, transaction safety levels, and how it provides high availability and redundancy compared to other SQL Server features like failover clustering and log shipping. It also provides best practices for configuring and monitoring database mirroring for mission critical databases.
Deep dive Developer Productivity and Performance SOA Suite 12c. Presentation during the SOA track of the AMIS SOA and BPM Suite 12c launch event on July 17, 2014
AAI-2016 WebSphere Application Server Installation and Maintenance in the Ent...WASdev Community
WebSphere Application Server Installation and Maintenance in the Enterprise discusses best practices for installing and maintaining WebSphere Application Server in an enterprise environment. Key points include:
- Manual installation and updates are time-consuming, so tools like Install Factory and IBM Installation Manager were created to automate the process.
- Maintenance includes applying interim fixes and fix packs. Fix packs bundle preventative maintenance fixes that have undergone extensive regression testing.
- It is important to apply maintenance proactively to reduce outages and their associated costs. A single fix pack can contain hundreds of fixes for defects and security issues.
- Careful planning is required for maintenance including testing strategies, change management processes, and understanding impacts
This document provides an overview and agenda for a WebSphere Administration course. The key topics that will be covered in the course include troubleshooting and monitoring, WebSphere security, cell management, and scalability and clustering. Specifically, the document outlines sections on troubleshooting techniques and log files, enabling administrative and application security, configuring user account repositories, creating a WebSphere cell by adding nodes to a deployment manager profile, and setting up clusters for scalability.
Software architecture to analyze licensing needs for pcms- pegasus cargo ma...Shahzad
The document discusses licensing needs for the Pegasus Cargo Management System (PCMS) software. It provides information on SQL Server editions and licensing, including definitions of the different editions (e.g. Datacenter, Enterprise, Standard), their features and limitations. It also includes comparison charts summarizing the scalability, management tools, programmability, security, and reporting capabilities of each edition. The goal is to help determine the appropriate SQL Server edition licensing required to support the PCMS software.
Presentation by Bruce Campbell of Microsoft
Learn about a new capability in SQL Server 2008 R2, Parallel Data Warehouse, formerly known as Project Madison.
NZSPC 2013 - Ultimate SharePoint Infrastructure Best Practices SessionMichael Noel
Michael Noel is the author of 19 technical books on Microsoft technologies that have sold over 300,000 copies. He is a partner at Convergent Computing, an infrastructure and security consulting firm. The document provides hardware and software requirements for SharePoint 2013 environments, including recommended memory, processors, and editions of Windows Server and SQL Server. It also summarizes new features in SharePoint 2013 like the distributed cache service, request management, and claims-based authentication.
Effective Usage of SQL Server 2005 Database Mirroringwebhostingguy
The document discusses SQL Server 2005 database mirroring, including concepts like principal and mirror databases, transaction safety levels, and how it provides high availability and redundancy compared to other SQL Server features like failover clustering and log shipping. It also provides best practices for configuring and monitoring database mirroring for mission critical databases.
Deep dive Developer Productivity and Performance SOA Suite 12c. Presentation during the SOA track of the AMIS SOA and BPM Suite 12c launch event on July 17, 2014
AAI-2016 WebSphere Application Server Installation and Maintenance in the Ent...WASdev Community
WebSphere Application Server Installation and Maintenance in the Enterprise discusses best practices for installing and maintaining WebSphere Application Server in an enterprise environment. Key points include:
- Manual installation and updates are time-consuming, so tools like Install Factory and IBM Installation Manager were created to automate the process.
- Maintenance includes applying interim fixes and fix packs. Fix packs bundle preventative maintenance fixes that have undergone extensive regression testing.
- It is important to apply maintenance proactively to reduce outages and their associated costs. A single fix pack can contain hundreds of fixes for defects and security issues.
- Careful planning is required for maintenance including testing strategies, change management processes, and understanding impacts
This document provides an overview and agenda for a WebSphere Administration course. The key topics that will be covered in the course include troubleshooting and monitoring, WebSphere security, cell management, and scalability and clustering. Specifically, the document outlines sections on troubleshooting techniques and log files, enabling administrative and application security, configuring user account repositories, creating a WebSphere cell by adding nodes to a deployment manager profile, and setting up clusters for scalability.
IBM websphere application server types of profilesKuldeep Saxena
This document discusses various profiles in IBM Websphere Application Server Network Deployment. It describes the Application Server Profile which creates a standalone server, the Custom Profile which creates an empty node to add to a deployment manager, and several management profiles including the Deployment Manager Profile which manages nodes and servers, the Administrative Agent Profile which manages standalone servers on one machine, and the Job Manager Profile which provides centralized management across deployments. The Cell Profile combines a deployment manager and application server.
A How-to practical example of installing SAP HANA Dynamic Tiering, creating extended storage, provisioning to a tenant database and creating table using extended storage
The document discusses key concepts in IBM Websphere Application Server (WAS) including server, node, node group, cell, deployment manager, node agent, cluster, and profile. A server handles application requests and responses. A node is a configuration repository that can contain multiple servers. A node group contains similar nodes. A cell contains node groups, nodes, and servers and represents an entire deployment. A deployment manager centrally manages cells. Node agents facilitate communication between nodes and the deployment manager. A cluster groups application servers for high availability. A profile creates the configuration to deploy servers and cells.
The document provides an overview and agenda for a WebSphere Administration course. It covers topics like WebSphere and JEE overviews, WebSphere architecture, installing WebSphere, the admin console, managing applications, and JEE technologies. It also includes sections on WebSphere product families, the WebSphere application server, and WebSphere directory structure.
The document summarizes key topics from a SQL Server Users Group meeting in December 2006, including SQL Server 2005 licensing models, high availability options, virtualization, and other software licensing topics. It provides details on per processor and per server/per CAL licensing, virtualization rules, and SQL Server editions from Express to Enterprise. It also discusses the Service Provider License Agreement, acquiring licenses through partners, downgrade rights, and Software Assurance benefits.
Sun Microsystems introduced the JDBC driver and API in 1996 to allow Java programmers to interact with databases. The JDBC driver translates messages between the Java application and database using a specified protocol. There are four main types of JDBC drivers: Type 1 translates to ODBC, Type 2 uses native database APIs, Type 3 is all Java and uses a middleware server, and Type 4 also uses a proprietary protocol but is all Java. The basic JDBC process involves loading the driver, connecting to the database, executing SQL statements, processing result sets, and closing the connection.
This document provides an overview of Module 1 which introduces SQL Server 2008 R2 and its toolset. It covers the SQL Server platform architecture, components, instances, and editions. It also discusses tools for working with SQL Server like SQL Server Management Studio, Business Intelligence Development Studio, and Books Online. Finally, it reviews configuring SQL Server services, network ports, server aliases, and tools like SQL Server Profiler. The module includes exercises and a lab scenario to configure a new SQL Server instance for a separate company using an existing server.
The document summarizes features of SQL Server 2005 Mobile Edition and the .NET Compact Framework v2.0 for accessing data. It discusses the architecture, integration with SQL Server 2005 and Visual Studio 2005, and synchronization options including remote data access and merge replication. Key points covered include improved performance, query optimization, updated cursors, and ease of development in Visual Studio 2005.
Backing up the server parameter file is recommended for recovery purposes. This can be done using the CREATE PFILE statement to create a backup of the server parameter file. RMAN can also be used to create backups of the server parameter file. If the parameter file is lost, the database instance can be started using a client-side initialization parameter file and a new server parameter file created with CREATE SPFILE.
Oracle released version 12.2.5 of their E-Business Suite which includes several new features. Key new features for database administrators include a dualfs option that allows cloning of file systems in a single step, a central inventory to manage multiple instances, and a new ADOP utility to monitor and validate patching. Additional performance enhancements were made to Weblogic and the ADOP user interface was improved.
This document provides an overview and instructions for administering WebSphere resources such as JDBC and JMS. It begins with an introduction to JDBC data source administration including creating JDBC providers and data sources. Next it covers JMS administration including the JMS programming model, message types, and creating destinations using the default messaging provider. The document provides code samples and step-by-step instructions for common administration tasks.
WebSphere Application Server (WAS) provides the infrastructure to develop and run web and enterprise applications. It includes a web container to handle HTTP requests and servlets/JSPs, an EJB container to manage enterprise java beans, and various services like transactions, security, and messaging. WAS implements the J2EE specification and is available in different packages for single server or clustered/scalable environments. It supports the development and deployment of web services, SOA applications, and dynamic web sites.
The AlwaysOn Availability Groups feature is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. Introduced in SQL Server 2012, AlwaysOn Availability Groups maximizes the availability of a set of user databases for an enterprise
Sql Server 2012 overview and licensingRay Cochrane
- The document discusses Microsoft SQL Server 2012 licensing and migration options for customers with existing SQL Server 2008 R2 licenses.
- It provides licensing rules and examples for migrating from Standard, Enterprise, and Datacenter editions when customers have active Software Assurance on their existing licenses.
- Customers can migrate their existing server and CAL licenses or processor licenses to equivalent SQL Server 2012 editions based on their existing license type and level of processor cores or servers.
The document provides an overview of WebLogic Server topology, configuration, and administration. It describes key concepts such as domains, servers, clusters, Node Manager, and machines. It also covers configuration files, administration tools like the Administration Console and WLST, and some sample configuration schemes for development, high availability, and simplified administration.
Have you ever used Oracle WebLogic Server? If the answer is no, this presentation is for you. We explain core WebLogic Server concepts and perform a live walkthrough of the console covering core administration areas that include managed servers, JVM servers, JMS resources, logs, data sources, application deployments, and more.
Five Cool Use Cases for the Spring Component in Oracle SOA SuiteGuido Schmutz
Both Oracle SOA Suite and Oracle Unified Business Process Management Suite make it possible to embed Java code as a Service Component Architecture (SCA) first-class citizen through the Spring component implementation type. Thereby the coarse-grained components of Oracle SOA Suite are extended by the much-finer-grained Spring beans wrapped inside the Spring component. This session presents five cool use cases for the Spring component. It shows how and why you would want to use the Spring component and will hopefully inspire attendees to use it for their own projects.
This document discusses high availability considerations for SQL Server backends in SharePoint 2010 environments. It covers why high availability is important, various SQL Server high availability and disaster recovery technologies like database mirroring and failover clustering. It also provides best practices for SQL Server and database configuration to optimize performance, including storage configuration, tempdb and content database settings. The presentation demonstrates configurations for failover clustering and database mirroring and shows how to check database health and optimization.
Application developers are the customers of your API. Success is measured by how quickly those developers enjoy success using your API in their applications. And rapid adoption of an API by your internal, partner, or external developers is all about design.
Building upon their prior work in API design, Marsh Gardiner and Brian Mulloy unveil RV, a style of API design that embraces developer adoption as its guiding principle. They explore the constraints and opportunities introduced by RV and discuss RV's place in the context of other design approaches like REST and Hypermedia.
See the youtube video of this webcast https://www.youtube.com/watch?v=u-bGz9HQIuo
By Dale Vile
Evolution of licensing models
Virtualization related considerations
A scenario based analysis of options
Other licensing considerations
Top line recommendations
Comments and questions
IBM websphere application server types of profilesKuldeep Saxena
This document discusses various profiles in IBM Websphere Application Server Network Deployment. It describes the Application Server Profile which creates a standalone server, the Custom Profile which creates an empty node to add to a deployment manager, and several management profiles including the Deployment Manager Profile which manages nodes and servers, the Administrative Agent Profile which manages standalone servers on one machine, and the Job Manager Profile which provides centralized management across deployments. The Cell Profile combines a deployment manager and application server.
A How-to practical example of installing SAP HANA Dynamic Tiering, creating extended storage, provisioning to a tenant database and creating table using extended storage
The document discusses key concepts in IBM Websphere Application Server (WAS) including server, node, node group, cell, deployment manager, node agent, cluster, and profile. A server handles application requests and responses. A node is a configuration repository that can contain multiple servers. A node group contains similar nodes. A cell contains node groups, nodes, and servers and represents an entire deployment. A deployment manager centrally manages cells. Node agents facilitate communication between nodes and the deployment manager. A cluster groups application servers for high availability. A profile creates the configuration to deploy servers and cells.
The document provides an overview and agenda for a WebSphere Administration course. It covers topics like WebSphere and JEE overviews, WebSphere architecture, installing WebSphere, the admin console, managing applications, and JEE technologies. It also includes sections on WebSphere product families, the WebSphere application server, and WebSphere directory structure.
The document summarizes key topics from a SQL Server Users Group meeting in December 2006, including SQL Server 2005 licensing models, high availability options, virtualization, and other software licensing topics. It provides details on per processor and per server/per CAL licensing, virtualization rules, and SQL Server editions from Express to Enterprise. It also discusses the Service Provider License Agreement, acquiring licenses through partners, downgrade rights, and Software Assurance benefits.
Sun Microsystems introduced the JDBC driver and API in 1996 to allow Java programmers to interact with databases. The JDBC driver translates messages between the Java application and database using a specified protocol. There are four main types of JDBC drivers: Type 1 translates to ODBC, Type 2 uses native database APIs, Type 3 is all Java and uses a middleware server, and Type 4 also uses a proprietary protocol but is all Java. The basic JDBC process involves loading the driver, connecting to the database, executing SQL statements, processing result sets, and closing the connection.
This document provides an overview of Module 1 which introduces SQL Server 2008 R2 and its toolset. It covers the SQL Server platform architecture, components, instances, and editions. It also discusses tools for working with SQL Server like SQL Server Management Studio, Business Intelligence Development Studio, and Books Online. Finally, it reviews configuring SQL Server services, network ports, server aliases, and tools like SQL Server Profiler. The module includes exercises and a lab scenario to configure a new SQL Server instance for a separate company using an existing server.
The document summarizes features of SQL Server 2005 Mobile Edition and the .NET Compact Framework v2.0 for accessing data. It discusses the architecture, integration with SQL Server 2005 and Visual Studio 2005, and synchronization options including remote data access and merge replication. Key points covered include improved performance, query optimization, updated cursors, and ease of development in Visual Studio 2005.
Backing up the server parameter file is recommended for recovery purposes. This can be done using the CREATE PFILE statement to create a backup of the server parameter file. RMAN can also be used to create backups of the server parameter file. If the parameter file is lost, the database instance can be started using a client-side initialization parameter file and a new server parameter file created with CREATE SPFILE.
Oracle released version 12.2.5 of their E-Business Suite which includes several new features. Key new features for database administrators include a dualfs option that allows cloning of file systems in a single step, a central inventory to manage multiple instances, and a new ADOP utility to monitor and validate patching. Additional performance enhancements were made to Weblogic and the ADOP user interface was improved.
This document provides an overview and instructions for administering WebSphere resources such as JDBC and JMS. It begins with an introduction to JDBC data source administration including creating JDBC providers and data sources. Next it covers JMS administration including the JMS programming model, message types, and creating destinations using the default messaging provider. The document provides code samples and step-by-step instructions for common administration tasks.
WebSphere Application Server (WAS) provides the infrastructure to develop and run web and enterprise applications. It includes a web container to handle HTTP requests and servlets/JSPs, an EJB container to manage enterprise java beans, and various services like transactions, security, and messaging. WAS implements the J2EE specification and is available in different packages for single server or clustered/scalable environments. It supports the development and deployment of web services, SOA applications, and dynamic web sites.
The AlwaysOn Availability Groups feature is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. Introduced in SQL Server 2012, AlwaysOn Availability Groups maximizes the availability of a set of user databases for an enterprise
Sql Server 2012 overview and licensingRay Cochrane
- The document discusses Microsoft SQL Server 2012 licensing and migration options for customers with existing SQL Server 2008 R2 licenses.
- It provides licensing rules and examples for migrating from Standard, Enterprise, and Datacenter editions when customers have active Software Assurance on their existing licenses.
- Customers can migrate their existing server and CAL licenses or processor licenses to equivalent SQL Server 2012 editions based on their existing license type and level of processor cores or servers.
The document provides an overview of WebLogic Server topology, configuration, and administration. It describes key concepts such as domains, servers, clusters, Node Manager, and machines. It also covers configuration files, administration tools like the Administration Console and WLST, and some sample configuration schemes for development, high availability, and simplified administration.
Have you ever used Oracle WebLogic Server? If the answer is no, this presentation is for you. We explain core WebLogic Server concepts and perform a live walkthrough of the console covering core administration areas that include managed servers, JVM servers, JMS resources, logs, data sources, application deployments, and more.
Five Cool Use Cases for the Spring Component in Oracle SOA SuiteGuido Schmutz
Both Oracle SOA Suite and Oracle Unified Business Process Management Suite make it possible to embed Java code as a Service Component Architecture (SCA) first-class citizen through the Spring component implementation type. Thereby the coarse-grained components of Oracle SOA Suite are extended by the much-finer-grained Spring beans wrapped inside the Spring component. This session presents five cool use cases for the Spring component. It shows how and why you would want to use the Spring component and will hopefully inspire attendees to use it for their own projects.
This document discusses high availability considerations for SQL Server backends in SharePoint 2010 environments. It covers why high availability is important, various SQL Server high availability and disaster recovery technologies like database mirroring and failover clustering. It also provides best practices for SQL Server and database configuration to optimize performance, including storage configuration, tempdb and content database settings. The presentation demonstrates configurations for failover clustering and database mirroring and shows how to check database health and optimization.
Application developers are the customers of your API. Success is measured by how quickly those developers enjoy success using your API in their applications. And rapid adoption of an API by your internal, partner, or external developers is all about design.
Building upon their prior work in API design, Marsh Gardiner and Brian Mulloy unveil RV, a style of API design that embraces developer adoption as its guiding principle. They explore the constraints and opportunities introduced by RV and discuss RV's place in the context of other design approaches like REST and Hypermedia.
See the youtube video of this webcast https://www.youtube.com/watch?v=u-bGz9HQIuo
By Dale Vile
Evolution of licensing models
Virtualization related considerations
A scenario based analysis of options
Other licensing considerations
Top line recommendations
Comments and questions
Este documento describe dos sitios web 2.0: YouTube, un sitio para compartir videos donde los usuarios pueden subir y compartir clips de películas, programas y música usando un reproductor basado en Adobe Flash o HTML5, y SlideShare, un sitio para compartir presentaciones donde los usuarios pueden subir y compartir presentaciones en formatos como PowerPoint, PDF y Word.
This document defines and explains the concepts of value-based pricing. It discusses that value-based pricing sets the price based on the value an offering delivers to customers compared to their next best alternative. It notes that value is customer-specific, measured in currency, and relative to the next best alternative. The document also discusses how understanding value is important for proper customer segmentation, targeting the right segments, and developing products customers are willing to buy. It provides an example of how willingness to pay is driven by the sense of loss if a customer's need is not resolved. Finally, it states that once value is defined, customers' willingness to pay is determined, and there is interest in a segment, an offering can be designed to deliver
This executive summary explains why we released an updated version of the Platform Design Toolkit - The definitive set of design thinking and system modeling tools to design digital and non digital Platforms to access powerful Ecosystems and reach objectives way beyond the boundaries of your firm.
For More information on the Toolkit visit: www.platformdesigntoolkit.com
For more complete presentation and context post see: http://meedabyte.com/2015/11/06/platform-design-toolkit-2-0-open-for-comments/
This is an updated release:
First, I released the Platform Design Canvas alone, then I added the Platform Motivations Matrix to a newly born "toolkit" made of different tools (most of them are still in the making).
Here you can find a context post with a step by step guide to using this preliminary version of the toolkit: http://bit.ly/PDToolkitGuide
The document defines variances as differences between standard and actual costs. It discusses computing variances for material costs, including material cost, price, usage, mix, and yield variances. It also discusses labor cost and rate variances. Variances are classified and examples are provided to demonstrate how to calculate different types of variances based on standard and actual data. The key information is on defining and calculating different types of variances to identify reasons for deviations between actual and standard performance.
This document provides an overview of SQL Server clustering. SQL Server clustering uses Microsoft clustering services (MSCS) to set up a highly available Windows cluster for mission critical databases. There are two main failover configurations - active/passive where only one node is active and active/active where both nodes are active. The top three challenges to implementing a cluster are managing CPU, memory, and disk resources to allow for failover without degrading performance. Proper planning and design is important to ensure a smooth clustered SQL Server environment.
This document summarizes new features in SQL Server 2008 R2 including management, scalability, availability, and business intelligence enhancements. Key updates include improved multi-server management with the SQL Server Utility, data-tier application management, increased virtualization support through Hyper-V, Master Data Services, StreamInsight for complex event processing, PowerPivot for self-service reporting, and new premium editions for high scalability. It also provides an overview of SQL Server 2008 R2 editions and licensing changes.
Sql server 2019 New Features by Yevhen NedaskivskyiAlex Tumanoff
SQL Server 2019 introduces several new high availability and disaster recovery features such as support for up to 5 synchronous replicas in an Always On availability group and improved connection redirection capabilities. It also enhances PolyBase integration and provides new options for certificate management across instances. Additional new features include support for persistent memory, columnstore index improvements, and resumable online index operations.
The document provides an overview and agenda for a presentation on Windows Azure SQL Database tips and tricks for beginners. The presentation covers SQL Azure analysis including security requirements, compatibility with different SQL Server versions, scenarios for use, and the shared environment. It also demonstrates SQL Azure features in the Azure mode and discusses the future of database administration.
This document provides an overview of SQL Server clustering. It discusses the importance of high availability and introduces some key concepts in clustering like nodes, shared storage, heartbeats, failover and failback. It also covers the basic architecture of a SQL Server cluster, including the virtual server and different types of clusters. Some advantages and disadvantages of clustering are outlined. Finally, it discusses some terminology used in clustering and provides a checklist for preparing Windows clustering.
In Zusammenarbeit mit Microsoft und SofwareOne AG konnten wir am 3. Februar 2016 einen Workshop zur Microsoft-SQL-Lizenzierung durchführen. Die Referenten Alexander Egli, Beat Weissenberger und Detlef Werner gaben den Teilnehmern einen detaillierten Überblick über die Änderungen in der Lizenzierung von SQL Server 2012 sowie der aktuellen Lizenzierung von SQL Server 2014. Für die Version 2014 wurden folgende Szenarien besprochen:
Core-Lizenzierung
Lizenzierung in virtuellen Umgebungen
Hybride Szenarien mit Integration von Cloud-Komponenten
Ebenfalls wurden die Migration und Kostenbeispiele besprochen.
The Evolution of SQL Server as a Service - SQL Azure Managed InstanceJavier Villegas
Managed Instance provides a fully managed SQL Server database hosted on Azure PaaS that allows existing SQL Server applications to be migrated to the cloud with minimal changes. It provides near 100% compatibility with on-premises SQL Server along with the management and scalability benefits of PaaS. Key capabilities include built-in high availability, automated backups, isolation within a VNet, and the ability to migrate databases with minimal downtime.
Modern Cloud-Native Streaming Platforms: Event Streaming Microservices with A...confluent
Microservices, events, containers, and orchestrators are dominating our vernacular today. As operations teams adapt to support these technologies in production, cloud-native platforms like Pivotal Cloud Foundry and Kubernetes have quickly risen to serve as force multipliers of automation, productivity and value.
Apache Kafka® is providing developers a critically important component as they build and modernize applications to cloud-native architecture.
This talk will explore:
• Why cloud-native platforms and why run Apache Kafka on Kubernetes?
• What kind of workloads are best suited for this combination?
• Tips to determine the path forward for legacy monoliths in your application portfolio
• Demo: Running Apache Kafka as a Streaming Platform on Kubernetes
Windows Server clustering provides high availability and scalability. It allows groups of independent servers to work together as a single system. There are two types of clusters - Network Load Balancing Clusters and Server Clusters. Network Load Balancing Clusters balance load without high availability, while Server Clusters use clustering software to provide redundancy and failover capability. DHCP failover allows two DHCP servers to share scope information including active leases, enabling either server to provide addresses if the other fails.
This document discusses MySQL Cluster, a distributed database that provides high availability, scalability and real-time performance. It summarizes MySQL Cluster's key capabilities like auto-sharding, ACID compliance, high scalability for reads and writes, self-healing capabilities and more. It also discusses how MySQL Cluster is used by various companies and provides overviews of the MySQL Cluster architecture, scaling and high availability features.
Maintenance Plans for Beginners (but not only) | Each of experienced administrators used (to some extent) what is called Maintenance Plans - Plans of Conservation. During this session, I'd like to discuss what can be useful for us to provide functionality when we use them and what to look out for. Session at 200 times the forward-300, with the opening of the discussion.
MySQL London Tech Tour March 2015 - MySQL FabricMark Swarbrick
This document discusses MySQL Fabric, which is a framework for managing high availability and sharding of MySQL servers. It provides simple and transparent high availability through automatic failover and replication management. It also allows scaling out through sharding where application data is partitioned across multiple MySQL servers. MySQL Fabric handles routing of queries to appropriate servers and coordination between servers to enable features like global updates, shard splitting and moving.
MySQL Cluster - Latest Developments (up to and including MySQL Cluster 7.4)Andrew Morgan
MySQL Cluster is the distributed, shared-nothing version of MySQL. It’s typically used for applications that need any combination of high availability, real-time performance, and scaling of reads and writes. After a brief introduction to the technology, its uses, and the new features added in MySQL Cluster 7.3, this session focuses on the very latest developments happening in MySQL Cluster 7.4. As you’d expect from a real-time, scalable, distributed, in-memory database, performance continues to be a top priority, as do simplicity of use and robustness. Come hear firsthand what’s being done to make sure MySQL Cluster continues to dominate in mission-critical, high-performance applications.
Deep dive session - running microsoft applications in the cloudRitesh Toshniwal
- Microsoft Active Directory can be deployed on AWS to provide authentication, authorization, and directory services for workloads running in AWS. This allows extending on-premises Active Directory to the cloud.
- There are two main options - using AWS Directory Service to deploy managed Microsoft AD in AWS, or setting up trust relationships between on-premises AD and an AD deployed in a VPC using EC2 instances.
- AWS Directory Service allows redirecting directory requests in AWS to the on-premises AD without caching information in the cloud.
This document provides an overview of SQL Server DBA training topics including:
- Installing and configuring SQL Server, choosing the appropriate edition, and installing service packs
- Security concepts including logins and users
- Administrative tasks such as backups, restores, monitoring, and high availability that DBAs are responsible for
This document provides an overview of SQL Server DBA training topics including:
- Installing and configuring SQL Server, including choosing an edition, installation process, and configuring services
- Security topics such as logins and users
- Additional administrative tasks like managing database files, backups, restores, monitoring, maintenance plans, and high availability options
- Appendices with differences between SQL and Oracle and an installation guide with screenshots
Adaptive Server Farms for the Data Centerelliando dias
The document discusses adaptive server farms for data centers. It addresses challenges like inefficient utilization, overprovisioning, and high costs. It proposes pooling server resources, automating management, and dynamically allocating resources based on demand. This improves utilization and reduces costs through automation, load balancing, and continuous service availability.
Spring Cloud Services with Pivotal Cloud Foundry- Gokhan GoksuVMware Tanzu
- Pivotal Cloud Foundry (PCF) is a cloud application platform that supports Spring applications. It provides automated deployment of Spring and Spring Boot apps along with a services ecosystem.
- Spring Cloud Services (SCS) provides services for PCF like service registry, configuration management, and circuit breakers that integrate with Spring apps. It includes tools to manage credentials and integrate apps with services.
- The document discusses how PCF supports developers through services, buildpacks, and automation to deploy Spring apps and discusses integrating apps with services through SCS. It also provides an agenda for a demo of deploying Spring apps on PCF.
Hpe service virtualization 3.8 what's new chicago admJeffrey Nunn
Service Virtualization is an HPE branded solution that helps simulate and emulate the behavior of specific components in heterogeneous component-based applications such as API-driven apps, ERP apps, cloud-based apps, and web services/service-oriented architectures (SOA).
Value Proposition
Empowers developers and testers to easily automate, predict, accelerate and scale their application testing and delivery through virtualization and simulation of dependent components and services that are either off limits, unavailable, inaccessible, or with costly fees to access.
Similar to KoprowskiT_SQLSat152_WelcomeToTheLicensingNightmare (20)
Session form series of conferences during Data Relay (formerly SQL Relay) 2018 in Newcastle, Leeds, Birmingham, Reading, Bristol. The session contains only slides form the talk (no videos included).
Slides from data MindsConnect 2018 Conference hosted at Ghelamnco Arena in Ghent by Belgian SQL Server USer Grup. SECDev(OPS) How to embrace your security.
Session from SQLDay 2016 Conference in Wroclaw.
2 AM. We're sleeping well and our mobile is ringing and ringing. Message: DISASTER! In this session (on slides) we are NOT talking about the potential disaster (such BCM); we talk about: What happened NOW? Which tasks should have been finished BEFORE. Does virtual or physical SQL Server matter? We talk about systems, databases, people, encryption, passwords, certificates and users. In this session (on few demos) I'll show which part of our SQL Server environment are critical and how to be prepared for disaster. In some documents, I'll show You how to be BEST prepared.
Backup? Who cares! Now and Then? We store our data in the cloud. Somewhere in the Cloud. Which Cloud? Who cares! But we are still SQL Server Professionals, so… are we need backup? Should we use newest opportunities or old methods? Are we going a step further or step back? On my session, I will try to find answers for all of those (and more) questions. Demos, cases, and examples from the world of backup. And of course worst practices.
Our data should be secure. And our environment too. What we can do for maximizing security in a hybrid environment, where SQL Server exist in two forms: premise and cloud. How to organize our job, how to control our data if we use Windows Azure SQL Database - The Cloud Database. physical security, policy-based management, auditing, encryption, federation, access and authorization. All of those subjects will be covered during my session.
• We sleeping well. And our mobile ringing and ringing. Message: DISASTER! In this session (on slides) we are NOT talk about potential disaster (such BCM); we talk about: And what NOW? New version old my old well-known session updated for whole changes which happened in DBA World in last two-three years.
• So, from the ground to the Sky and further - everything for surviving disaster. Which tasks should have been finished BEFORE. Is virtual or physical SQL matter? We talk about systems, databases, peoples, encryption, passwords, certificates and users.
• In this session (on few demos) I'll show which part of our SQL Server Environment are critical and how to be prepared to disaster. In some documents I'll show You how to be BEST prepared.
On my first session I would to introduce everyone to formerly known SQL Azure (actually Windows Azure SQL Database). Under Tips and Trick session I will show which points, features, compatibility and non-compatibility for SQL Azure are important for DBA's. I will cover functionalities, performance, cost, and sla and security aspects.
After break I will show how we can work with our data in the Cloud using SQL Azure, Blob Storage, what functionality of backup, restore, encryption and availability are available for us, how we can implement hybrid environment and when an why it is (or not) good practice.
And finally I hope we will find few minutes for discussion about Future of the DBA (not only in AD 2016)
This document discusses best practices for preparing for and responding to a disaster involving critical IT systems like servers and databases. It emphasizes the importance of regular backups, having recovery procedures documented, testing restores, and defining roles and responsibilities of team members. It provides guidance on backup strategies for SQL Server and SharePoint, including using different types of backups, storing backups offline, and setting backup schedules. It also stresses the value of preparation, being ready to restore from backups, and having contact information and credentials documented in advance in case of an emergency.
Windows Azure SQL Database for Beginners (tips & tricks)
The document provides an overview and introduction to Windows Azure SQL Database including:
- Key features such as scalability, availability, data protection, and programmatic DBA functionality.
- Performance levels are described in DTU (database transaction units) with different tiers for Basic, Standard, and Premium databases.
- Limitations are discussed around database sizing, collations, logins/users, and compatibility with on-premises SQL Server features.
This document discusses SQL Server security enhancements in SQL Server 2014. It covers three main topics:
1) Transparent Data Encryption allows encrypting database and log files for protection both during operations and when backing up to disk or Azure. Encryption can use passwords, asymmetric keys, or certificates.
2) Encryption Key Management allows managing encryption keys through PowerShell, SMO, SSMS and T-SQL. Asymmetric keys or certificates used for encryption must be properly backed up.
3) A new "CONNECT ANY DATABASE" permission allows logins to connect to all current and future databases without other permissions in those databases. This facilitates auditing processes.
The document discusses SQL Server security in three parts. The first part provides an overview of security concepts and categories security into the IT, physical, and political realms. The second part outlines SQL Server security best practices such as using Windows authentication, securing administrator accounts, and limiting public permissions. The third part covers new security enhancements in SQL Server 2014 like transparent data encryption, encryption key management, and the CONNECT ANY DATABASE permission.
This document discusses SQL Server backup and recovery best practices. It begins with an introduction by Tobiasz Janusz Koprowski on his background and experience. The agenda then outlines parts on introduction to backup options, demonstrations of backup in the cloud and on-premise, and best practices. It covers topics like understanding different cloud service models, security requirements for Azure, and non-compatible features between SQL Server versions and SQL Azure. It also demonstrates connecting to and backing up databases in SQL Azure and on-premise SQL Server.
This document discusses SQL Server security and provides an overview of SQL Server security best practices and enhancements in SQL Server 2014. It covers categorizing security across IT, physical, political, and SQL Server realms. It outlines best practices for authentication, securing administrator accounts, complex passwords, specific logins, administrator membership, guest access, stored procedure permissions, ports, services, and encryption. New SQL Server 2014 features discussed include transparent data encryption, encryption key management, and new permissions for connecting to any database and impersonating logins.
This document provides an overview and agenda for a presentation on Windows Azure SQL Database for beginners. The presentation will cover topics in three parts: features and functionality of SQL Database in Azure in the first part, demonstrations of the Azure portal and management tools in the second part, and a discussion on the future of database administration in the third part. Additional links and a question/answer session will be provided in an appendix.
SQL Server Source Control for Beginners is a presentation about using source control for SQL Server databases. It discusses:
- Common source control systems like SVN, TFS, and Mercurial that can be used to track database changes.
- How RedGate SQL Source Control allows committing database objects and changes directly from SQL Server Management Studio.
- Key features like rolling back changes, maintaining referential integrity, and locking objects while working.
- Demonstrates setting up a database in source control and committing changes.
- Additional tools that can deploy databases directly from source control like SQL Compare and SQL Data Compare.
This document provides an overview and introduction to Windows Azure SQL Database. It discusses key topics such as:
- SQL Database service tiers including Basic, Standard, and Premium, which are differentiated by performance levels measured in Database Transaction Units (DTUs) and other features.
- Database size limits and performance metrics for each tier.
- Database replication and high availability capabilities to ensure reliability.
- Support for common SQL Server features while noting some limitations compared to on-premises SQL Server.
- Considerations for database naming, users/logins, migrations, and automation in the SQL Database platform.
- Indexing requirements and compatibility differences to be aware of.
Tobiasz Janusz Koprowski presents information on disaster preparedness and recovery best practices. The document discusses the importance of having backups, recovery procedures, clearly defined roles and responsibilities, service level agreements, and contact information in case of an outage. Specific recommendations include regularly testing restores, storing backup files offsite, having accurate documentation, and ensuring key personnel are prepared to respond to disasters and outages.
Maintenance plans provide a way to automate database maintenance tasks such as integrity checks, index maintenance, and backups. They can be created using the Maintenance Plan Wizard or Maintenance Plan Designer. Common tasks include checking database integrity with DBCC CHECKDB, reorganizing or rebuilding indexes, updating statistics, and performing full, differential or transaction log backups. Care must be taken to choose the right tasks and schedule to maintain performance and protect the database.
The document discusses best practices for preventing and recovering from disasters affecting IT systems. It emphasizes the importance of being prepared through regular backups, testing restores, clear documentation of backup and restore procedures, and defined roles and responsibilities. Key recommendations include performing backups to separate storage regularly; testing restores from backups; having a disaster recovery plan, procedures, and environment ready; and ensuring appropriate staff are assigned roles to respond to an outage. The overall message is that the best way to survive a disaster is through preparation, including backups, documentation, training and assigning roles.
This document provides an overview of wound healing, its functions, stages, mechanisms, factors affecting it, and complications.
A wound is a break in the integrity of the skin or tissues, which may be associated with disruption of the structure and function.
Healing is the body’s response to injury in an attempt to restore normal structure and functions.
Healing can occur in two ways: Regeneration and Repair
There are 4 phases of wound healing: hemostasis, inflammation, proliferation, and remodeling. This document also describes the mechanism of wound healing. Factors that affect healing include infection, uncontrolled diabetes, poor nutrition, age, anemia, the presence of foreign bodies, etc.
Complications of wound healing like infection, hyperpigmentation of scar, contractures, and keloid formation.
Level 3 NCEA - NZ: A Nation In the Making 1872 - 1900 SML.pptHenry Hollis
The History of NZ 1870-1900.
Making of a Nation.
From the NZ Wars to Liberals,
Richard Seddon, George Grey,
Social Laboratory, New Zealand,
Confiscations, Kotahitanga, Kingitanga, Parliament, Suffrage, Repudiation, Economic Change, Agriculture, Gold Mining, Timber, Flax, Sheep, Dairying,
Chapter wise All Notes of First year Basic Civil Engineering.pptxDenish Jangid
Chapter wise All Notes of First year Basic Civil Engineering
Syllabus
Chapter-1
Introduction to objective, scope and outcome the subject
Chapter 2
Introduction: Scope and Specialization of Civil Engineering, Role of civil Engineer in Society, Impact of infrastructural development on economy of country.
Chapter 3
Surveying: Object Principles & Types of Surveying; Site Plans, Plans & Maps; Scales & Unit of different Measurements.
Linear Measurements: Instruments used. Linear Measurement by Tape, Ranging out Survey Lines and overcoming Obstructions; Measurements on sloping ground; Tape corrections, conventional symbols. Angular Measurements: Instruments used; Introduction to Compass Surveying, Bearings and Longitude & Latitude of a Line, Introduction to total station.
Levelling: Instrument used Object of levelling, Methods of levelling in brief, and Contour maps.
Chapter 4
Buildings: Selection of site for Buildings, Layout of Building Plan, Types of buildings, Plinth area, carpet area, floor space index, Introduction to building byelaws, concept of sun light & ventilation. Components of Buildings & their functions, Basic concept of R.C.C., Introduction to types of foundation
Chapter 5
Transportation: Introduction to Transportation Engineering; Traffic and Road Safety: Types and Characteristics of Various Modes of Transportation; Various Road Traffic Signs, Causes of Accidents and Road Safety Measures.
Chapter 6
Environmental Engineering: Environmental Pollution, Environmental Acts and Regulations, Functional Concepts of Ecology, Basics of Species, Biodiversity, Ecosystem, Hydrological Cycle; Chemical Cycles: Carbon, Nitrogen & Phosphorus; Energy Flow in Ecosystems.
Water Pollution: Water Quality standards, Introduction to Treatment & Disposal of Waste Water. Reuse and Saving of Water, Rain Water Harvesting. Solid Waste Management: Classification of Solid Waste, Collection, Transportation and Disposal of Solid. Recycling of Solid Waste: Energy Recovery, Sanitary Landfill, On-Site Sanitation. Air & Noise Pollution: Primary and Secondary air pollutants, Harmful effects of Air Pollution, Control of Air Pollution. . Noise Pollution Harmful Effects of noise pollution, control of noise pollution, Global warming & Climate Change, Ozone depletion, Greenhouse effect
Text Books:
1. Palancharmy, Basic Civil Engineering, McGraw Hill publishers.
2. Satheesh Gopi, Basic Civil Engineering, Pearson Publishers.
3. Ketki Rangwala Dalal, Essentials of Civil Engineering, Charotar Publishing House.
4. BCP, Surveying volume 1
A Visual Guide to 1 Samuel | A Tale of Two HeartsSteve Thomason
These slides walk through the story of 1 Samuel. Samuel is the last judge of Israel. The people reject God and want a king. Saul is anointed as the first king, but he is not a good king. David, the shepherd boy is anointed and Saul is envious of him. David shows honor while Saul continues to self destruct.
3. SELECT {BIO}
Polish SQL Server User Group Leader
Microsoft Certified Trainer
MCP, MCSA, MLSS, MLSBS, MCTS, MCITP, MCT
SQL Server MVP from 2010
Friends of RedGate PLUS
PASS SQL Azure Virtual Chapter Co-Founder
Blogger, Influencer, Technical Writer
Last 7 years (living) in Data Center in Wrocław
Generally about 12 years in IT/banking area
GITCA Technical Lead & Vice-Chair EMEA Board
Speaker at SQL Server Community Launch, Time for SharePoint,
CodeCamps, SharePoint Community Launch, CISSP Day, InfoTRAMS,
SQLSaturday, SQLBits, CarreerCon,
Autor of few articles on TechNet (PL) and WSS.pl portal
Deep Dives Co-Author:
High availability of SQL Server in the context
of Service Level Agreements (Chapter 18th)
Working for MS Subject Matter Expert and MS Terminology
community (Windows 7, 8 & Visualstudio 2010,2011
4. SESSION AGENDA
Introduction
Licensing Models (Server, CAL, Processor), Licensing Programs
SQL Server 2008
Editions, Multiplexing, Passive Servers - HA solution, Multiprocessing,
Virtualization, Licensing of business solutions, SQL Server Client Access
Licenses CAL
SQL Server 2012
Editions, Licensing Model, Core-Based again
Responsibility
5 Dollars (not 5 cents)
Summary
Links
Q&A
6. INTRODUCTION | LICENSING MODELS - Licensing per
Server & Client /Device
SQL Server 2008 can be purchased as a server license (for Workgroup editions, Standard and
Enterprise), in conjunction with CALs on a device or user. This licensing mode is designed for
customers who do not use SQL Server in scenarios that require public access to the Internet.
Server license (for Workgroup editions, Standard and Enterprise)is required for each operating
system under the control of which you are running a particular edition of SQL Server or any of its
components (for example, Analysis Services).
CAL per device. This license is required for each device (for example a personal computer,
workstation, terminal, PDA, cell phone, etc.) to access or use the services or functionality of Microsoft
SQL Server.
CAL per user. CAL SQL Server for the user is required to provide users(employees, customers,
partners, etc.) to access Microsoft SQL Server or use of its services or features. Model license for the
server plus user CAL will generally cheaper solution, if one user is using multiple devices (for example,
a user with a desktop computer, laptop, PDA, etc.).
CAL is not a program - it is a legal document granting a device or user the right to access the server.
A single license per device CAL grants the right of access from one device to multiple servers (Version
CAL must comply with the latest version of the software installed on the servers). A single license per
user CAL gives one user access rights to multiple servers.
7. INTRODUCTION | LICENSING MODELS - Licensing
per Server & Client/Device | RESTRICTIONS
CALfor SQL Server x32/x64
CAL for SQL Server 2008 & 2008 R2
CAL for Workgroup
8. INTRODUCTION | LICENSING MODELS
SQL Server 2008 is available in three licensing models:
Server plus device client access license (CAL).
Requires a license for the computer running the Microsoft server product,
as well as CALs for each client device.
Server plus user client access license (CAL).
Requires a license for the computer running the Microsoft server product,
as well as CALs for each user.
Processor license.
Requires a single license for each CPU in the operating system environment
running SQL Server. This license includes unlimited client device access.
12. SQL SERVER 2008 (R2) | VERSIONS & LICENSING
PROGRAMS
EA EAP SELE OPEN FPP OEM SPLA ISVR
CT
STANDARD X X X X X X X X
ENTERPRISE X X X X X X X
DATACENTER X X X X X X X
WEB X X X X
PARARELL WH X
WORKGROUP X X X X X X X
DEVELOPER X X X
13. SQL SERVER 2008 (R2) | MULTIPLEXING part one
Sometimes organizations develop network scenarios that use various
forms of hardware and/or software that reduce the number of devices
or users that directly access or use the software on a particular server,
often called multiplexing or pooling hardware or software.
Use of such multiplexing or pooling hardware and/or software does
not reduce the number of CALs required to access or use SQL Server
software. A CAL is required for each distinct device or user that is
connected to the multiplexing or pooling software or hardware front
end.
14. SQL SERVER 2008 (R2) | MULTIPLEXING part one and
half
Multiplexing. Users / devices that access a SQL server
indirectly require a CAL
15. SQL SERVER 2008 (R2) | MULTIPLEXING part two
This is true no matter how many tiers of hardware or software exist between the
SQL Server and the client devices that ultimately use its data, services or
functionality. An exception to this includes the manual transfer of data from
employee to employee.
For example, if an employee sends an Excel version of a report to another
employee, the receiving employee does not require a CAL (as long as the report
does not access a SQL Server in some way). An additional exception is
communication exclusively between SQL servers.
16. SQL SERVER 2008 (R2) | MULTIPLEXING part two and
half
Without Multiplexing
No CAL
required
User 1 Manually User 2
Windows Server CAL forward
required email
SQL Server With Multiplexing
No CAL
required
User 3 Manually
forward User 4
Pooling CAL
required email
hardware
or software
Multiplexing. Manual transfers of reports, that
subsequently don’t access a SQL Server don’t require CALs.
17. SQL SERVER 2008 (R2) | PASSIVE / ACTIVE / HA part one
Database mirroring is a SQL Server 2008 technology for increasing database
availability. Database mirroring transfers transaction log records directly from one
server to another and can quickly failover to the standby server.
Failover clustering. Failover clustering is a process in which the operating
system and SQL Server 2008 work together to provide availability in the event of an
application failure, hardware failure, or operating-system error. Failover clustering
provides hardware redundancy through a configuration in which mission-critical
resources are transferred from a failing machine to an equally configured server
automatically.
Backup Log-Shipping. Log-shipping increases a SQL Server database's
availability by automatically copying and restoring the database's transaction logs to
another database on a standby server. Because the standby database receives all
changes to the original database, it's an exact duplicate of the original database—out
of date only by the delay in the copy-and-load process. You then have the ability to
make the standby server a new primary server if the original primary server becomes
unavailable. When the original primary server becomes available again, you can make
it a new standby server—effectively reversing the servers' roles.
18. SQL SERVER 2008 (R2) | PASSIVE / ACTIVE / HA
part two
A passive server does not need a license, provided that the number of
processors in the passive server is equal or less than those of the active
server. The passive server can take the duties of the active server for 30 days.
Afterward, it must be licensed accordingly.
A passive server does not need a license, provided that the number of
processors in the passive server is equal or less than those of the active
server. The passive server can take the duties of the active server for 30 days.
Afterward, it must be licensed accordingly.
Database Mirroring and Failover Clustering are available for Standard and
Enterprise editions..
19. SQL SERVER 2008 (R2) | MULTIPROCESING
Multicore processors, which consist of multiple processing execution units
or “cores” on one chip (socket), are seen as a promising way to boost
computing power.
Microsoft has been driving thought leadership in this area by charging the
same amount per processor, regardless of how many cores are in the
processor.
In contrast, Oracle asks customers to multiply each “core” by different factors
depending on processor type.
IBM has a dual policy where customers with x86 platforms are charged per
processor and customers on IBM’s POWER5-based systems are charged per
core.
Single Core Dual Core Four Core
Processor Processor Processor
20. SQL SERVER 2008 (R2) | VIRTUALIZATION / per
SERVER + CAL part one
Workgroup and Standard editions now allow you to run any number of
instances of the server software in one physical or virtual operating
system environment on the licensed server at a time. Previously, only the
Enterprise edition of the Server license allowed multi-instancing. This is a
great incentive for customers to adopt the Server/CAL model.
For Enterprise edition, for each server to which you assign a software
license, you may run, at any one time, any number of instances of the
server software in one physical and any number of virtual operating system
environments on that server.
21. SQL SERVER 2008 (R2) | VIRTUALIZATION / per
SERVER + CAL part two
SQL SQL SQL SQL
WS WS WS WS
WS/ Virtualization layer
Server
This example shows the extra option available with the enterprise edition only.
Required license using additional rights for EE : 1 SQL Server License. Required licenses
for all other workgroup and standard:4 SQL Server licenses
22. SQL SERVER 2008 (R2) | VIRTUALIZATION / per
PROCESSOR part one
With Workgroup, Web, and Standard editions, for each server to which
you have assigned the required number of per processor licenses, you may
run, at any one time, any number of instances of the server software in
physical and virtual operating system environments on the licensed
server. However, the total number of physical and virtual processors used
by those operating system environments cannot exceed the number of
software licenses assigned to that server
For Enterprise edition there is an added option: if all physical processors in
a machine have been licensed, then you may run unlimited instances of
SQL server 2008 in one physical and an unlimited number of virtual
operating environments on that same machine.
23. SQL SERVER 2008 (R2) | VIRTUALIZATION / per
PROCESSOR part two
SQL SQL SQL SQL SQL
WS WS WS WS WS
Proc 1 Proc 2 Proc 3 Proc 4
WS/ Virtualization layer
Server
This example shows the extra option available with the enterprise edition only. Number
of proc licenses required for EE : 4 SQL Processor Licenses. Number of proc licenses
required for Standard, Workgroup: 5 SQL Processor licenses
24. SQL SERVER 2012 | VIRTUALIZATION / per
PROCESSOR part one
With Workgroup, Web, and Standard editions, for each server to which
you have assigned the required number of per processor licenses, you may
run, at any one time, any number of instances of the server software in
physical and virtual operating system environments on the licensed
server. However, the total number of physical and virtual processors used
by those operating system environments cannot exceed the number of
software licenses assigned to that server
For Enterprise edition there is an added option: if all physical processors in
a machine have been licensed, then you may run unlimited instances of
SQL server 2008 in one physical and an unlimited number of virtual
operating environments on that same machine.
25. SQL SERVER 2008 (R2) | BUSINESS SOLUTIONS
What are the Business Solutions in SQL Server 2008 (R2)?
Analysis Services
Reporting services
Integration services
You have two choice:
USE ON SAME SERVER EVERYTHING
USE ON DIFFERENT SERVERS YOU Business Solutions
Case One – everything on the same
server = 1 license
Case Two – everything on different
servers = 3 licenses
27. SQL SERVER 2012 | LICENSED EDITIONS
SQL Server 2012 has been released in 3 main editions:
Enterprise for mission critical applications and large scale data warehousing
Business Intelligence, a new product edition, providing premium corporate
and self-service BI
Standard for basic database, reporting and analytics capabilities
And what with the other editions?
available in Developer, Express and Compact editions.
Web Edition will be offered in a SPLA model only.
Datacenter Edition is retired with all capabilities now available in Enterprise.
Workgroup and Small business Editions are also retired.
28. SQL SERVER 2012 | LICENSING MODEL part one
SQL Server 2012 will continue to offer two licensing options – one based on
computing power, and one based on users or devices.
Enterprise Edition (EE) will be licensed based on compute capacity
measured in cores
Business Intelligence (BI) Edition will be available in the Server + CAL
model, based on users or devices
Standard Edition (SE) offers both licensing models to address basic
database workloads
29. SQL SERVER 2012 | LICENSING MODEL part two
Licensing Options Pricing**
SQL Server 2012 Editions Description Server
Core Based Open NL (US$)
+ CAL
High end datacenter,
Enterprise data warehousing $6,874 per Core
and BI capabilities
Main
Editions Enterprise BI and $8,592 per
Business Intelligence
High Scale Analytics Server*
$1,793 per Core,
Basic database and
Standard or $898 per
BI capabilities
Server*
Access to SQL
Client Access
Server databases $209 per CAL
License (CAL)
licensed per server
30. SQL SERVER 2012 | LICENSING MODEL part three
Server and Client Access License (CAL) Licensing
The Business Intelligence and Standard Editions will be available under
the Server and Client Access License (CAL) model.
This licensing model can be used when the number of users can be readily
counted (e.g., internal database applications).
To access a licensed SQL Server, each user must have a SQL Server CAL that
is the same version or newer (for example, to access a SQL Server 2008 SE
server, a user would need a SQL Server 2008 or 2012 CAL).
Each SQL Server CAL can provide access to multiple licensed SQL Servers,
including the new Business Intelligence Edition as well as Standard Edition
Servers and legacy Enterprise Edition Servers.
The SQL Server 2012 CAL price will increase by about 27%.
31. SQL SERVER 2012 | LICENSING MODEL part four
Core-Based Licensing
The Enterprise Edition and Standard Edition of SQL Server 2012 will
both be available under core-based licensing. Core-based licenses will
be sold in two-core packs.
To license a physical server, you must license all the cores in the server
with a minimum of 4 core licenses required for each physical processor
in the server.
Core licenses will be priced at ¼ the cost of a SQL Server 2008 R2
(EE/SE) processor license.
AMD systems have different requirements; see SQL Server 2012 Quick
Reference Guide.
33. SQL SERVER 2012 | Virtualization Licensing - Cloud
Optimized
ALWAYSON
Always On the Unknown Path to Licensing Virtual Environment
To license a VM with core licenses, purchase a core license for each virtual
core (virtual thread) allocated to the virtual machine (minimum of 4 core
licenses per VM).
To license a single VM with a server license (for Business Intelligence or
Standard only), buy the server license and buy matching SQL Server CALs
for each user.
Each licensed VM covered with Software Assurance (SA) can be moved
frequently within a server farm or to a third party hoster or cloud services
provider without buying additional SQL Server licenses
34. SQL SERVER 2012 | Virtualization Licensing – High
Density part one
MAXIMUM VIRTUALIZATION
You can by fully licensing the server (or server farm) with Enterprise Edition
core licenses and Software Assurance based on the total number of physical
cores on the servers. SA then enables the ability to run an unlimited
number of virtual machines to handle dynamic workloads and fully utilize
the hardware’s computing power.
You can’t license for unlimited virtualization with SQL Server 2008 R2 EE
Server + CAL. This was only a temporary use right grant with SA.
35. SQL SERVER 2012 | Virtualization Licensing – High
Density part two
36. SQL SERVER 2012 | Transition to New Licensing Model
part one
Enterprise Edition Server + CAL Licensing
New server licenses for SSEE (Server+Cal) model will only be available for
purchase through June 30th, 2012,
EA/EAP customers that buy SQL Enterprise Edition Servers will have until their next EA/EAP renewal
after June 30th, 2012 to purchase additional server licenses to complete currently planned projects.
After that, all new SQL Server Enterprise Edition deployments must be purchased per core.
All existing SSEE (Server+CAL) model with SA current when SQL Server 2012
launches can be upgraded to SQL Server 2012 at no additional cost, and SA
can be maintained (server+cal) to provide access to future updates.
These Legacy Enterprise Edition Servers remain licensed under the Server + CAL model and require
the appropriate version of the SQL Server CAL for users or devices.
Legacy SSEE licensed in (Server+CAL) deployments will be subject to a 20 core
per server license maximum. This core maximum applies both to new server
licenses and to prior version server licenses upgraded to 2012 with SA.
If you purchased SQL Server 2008 R2 Enterprise Edition in the Server + CAL model with Software
Assurance and at the launch of SQL Server 2012 are running on a server with > 20 physical cores,
contact your Microsoft representative for help transitioning to the new licensing model.
37. SQL SERVER 2012 | Transition to New Licensing Model
part two
SQL Server Processor licenses under SA
You have rights to upgrade to SQL Server 2012 at no additional cost. At the
subsequent renewal, You have the opportunity to renew into core licenses.
Enterprise and Standard processor licenses under SA are valued at a minimum
of 4 core
Datacenter processor licenses are valued at a minimum of 8 core
At the end of the current agreement term, customers should do a self-inventory
of systems currently running SQL Server, documenting the number of cores in
each processor in use with a SQL Server processor license covered with Software
Assurance.
This will enable customers to receive the appropriate SQL Server 2012 use rights moving forward
and will determine the core license exchange eligibility at renewal.
Customers should do this self-inventory using the Microsoft Assessment and Planning (MAP) Toolkit
or other inventory tools and processes to accurately archive a time/date stamped inventory of
hardware tied to SQL Server installations.
If customers do not perform the self-inventory, they will receive a value of 4 core licenses for each
Standard and Enterprise Edition processor and 8 EE core licenses per Datacenter Edition processor.
38. SQL SERVER 2012 | Transition to New Licensing Model
part three
45. RESPONSIBILITY | if you use a software
EXTRACT from:
Microsoft SQL Server 2008 Standard Edition End User License Agreement
18. NOT FAULT TOLERANT. THE SOFTWARE IS NOT FAULT TOLERANT. LICENSOR HAS
INDEPENDENTLY DETERMINED HOW TO USE THE SOFTWARE IN THE INTEGRATED SOFTWARE
APPLICATION OR SUITE OF APPLICATIONS THAT IT IS LICENSING TO YOU, AND MICROSOFT HAS
RELIED ON LICENSOR TO CONDUCT SUFFICIENT TESTING TO DETERMINE THAT THE SOFTWARE IS
SUITABLE FOR SUCH USE.
19. NO WARRANTIES BY MICROSOFT. YOU AGREE THAT IF YOU HAVE RECEIVED ANY
WARRANTIES WITH REGARD TO EITHER (A) THE SOFTWARE, OR (B) THE SOFTWARE APPLICATION
OR SUITE OF APPLICATIONS WITH WHICH YOU ACQUIRED THE SOFTWARE, THEN THOSE
WARRANTIES ARE PROVIDED SOLELY BY THE LICENSOR AND DO NOT ORIGINATE FROM, AND ARE
NOT BINDING ON, MICROSOFT.
20. NO LIABILITY OF MICROSOFT FOR CERTAIN DAMAGES. TO THE MAXIMUM EXTENT
PERMITTED BY APPLICABLE LAW, MICROSOFT SHALL HAVE NO LIABILITY FOR ANY INDIRECT,
SPECIAL, CONSEQUENTIAL OR INCIDENTAL DAMAGES ARISING FROM OR IN CONNECTION WITH
THE USE OR PERFORMANCE OF THE SOFTWARE OR THE SOFTWARE APPLICATION OR SUITE OF
APPLICATIONS WITH WHICH YOU ACQUIRED THE SOFTWARE, INCLUDING WITHOUT LIMITATION,
PENALTIES IMPOSED BY GOVERNMENT. THIS LIMITATION WILL APPLY EVEN IF ANY REMEDY
FAILS OF ITS ESSENTIAL PURPOSE.
IN NO EVENT SHALL MICROSOFT BE LIABLE FOR ANY AMOUNT IN EXCESS OF TWO
HUNDRED FIFTY U.S. DOLLARS (US$250.00).
48. LICENSING ASPECTS SUMMARY
Read Documentation
Read User Rights / EULA / PUR / SPUR
Check changes regullary
ASK MICROSOFT;
BETTER VIA MAIL THAN PHONE
BETTER MINIMUM TWO ADVISORS
REMEMBER (based on my experience):
1+2=3
Any 1 question for 2 advisors back in 3 answers
49. ATE | Ask The licensing Experts
· Insight
Daniel Verma Daniel.Verma@uk.insight.com
· Softcat
Damian Wakefield DamianWa@softcat.com
· Bytes
Rob Luppi rob.luppi@bytes.co.uk
· Comparex
Will Allmey William.Allmey@comparex.co.uk
Sarah Agate Sarah.Agate@comparex.co.uk
· Hewlett Packard
Phil Duncan Phil.Duncan@hp.com
· SoftwareOne
Kathy Jones Kathy.Jones@softwareone.com
50. LINKS | licensing
Microsoft Licensing Portal
https://partner.microsoft.com/UK/licensing
SQL Server 2012 Licensing
http://www.microsoft.com/sqlserver/en/us/get-sql-server/licensing.aspx
Microsoft Volume Licensing Portal
http://www.microsoft.com/licensing/
Microsoft Licensing Acreditation (only for license nerds)
https://partner.microsoft.com/UK/licensing/licensingtraining
Get Licensing Ready | The level 50 to 300 curriculum covers tracks for small and
medium businesses (SMBs) and large organisations - and provides self-service
online tutorials, data sheets and assessments.
Licensing Bootcamps | Join Microsoft and our Authorised Distributors for
classroom Licensing training, following our licensing curriculum.
SharePoint: Determining Your Licensing Needs
http://sharepoint.microsoft.com/en-us/buy/Pages/Licensing-Details.aspx
51. LINKS | user / provider rights
Microsoft Product Use Rights (PUR)
http://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&Do
cumentTypeId=1
Microsoft Services Provider Use Rights (SPUR)
http://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&Do
cumentTypeId=2
Microsoft End-User License Agreement (EULA)
* long address: www.google.co.uk/url?sa=t&rct=j&q=microsoft
eula&source=web&cd=2&ved=0CG4QFjAB&url=http%3A%2F%2Fdownload.mi
crosoft.com%2Fdocuments%2Fuseterms%2Fwindows%2520xp%2520sp2_profe
ssional_english_29e61d64-43e3-4ca3-b201-fe0c62507034.pdf&ei=WS2qT-
jjIcX-4QSw9fWpCQ&usg=AFQjCNH0jbItSRHv9l-HrNzyPFM2KOW3WQ
* short address: http://bit.ly/JdPvAi (thank You Bit.Ly !)
General End-User License Agreement (EULA)
WikiPedia http://en.wikipedia.org/wiki/End-user_license_agreement