SQL, noSQL, Entity Framework ? Hadoop ! ? Quelles options d'accès aux données pour vos applications hébergées dans AZURE ? Venez découvrir les "patterns" les mieux adaptés à vos applications "hybrides" ou complètement "azurés" et les possibilités de management qu'offre la plateforme Azure. La nouvelle fonctionnalité VM de Windows Azure permet désormais de déployer SQL Server en quelques clics. Mais est-ce la solution dont vous avez besoin pour vos données ? Dans cette session, vous obtiendrez un panorama complet des solutions de stockage avec Windows Azure, SQL ou noSQL et découvrirez pour chacune les avantages, scénarios clés, indications de prix et démonstrations ! (SQL Federation, SQL Server Data Sync seront également abordés)
Les données on-premise et dans le cloud. Quelles options ?
1. Les données dans le Cloud
et On-Premise. Quelles
Sébastien PERTUS DPE. Microsoft France
options ?
Francisco ORCHARD Consultant BI. AI3
http://blogs.msdn.com/b/mim/
http://www.ai3.fr
Code / Développement
5. SQL DANS AZURE
Windows
Machine
Azure SQL
Virtuelles
Database
6. Differences SQL IAAS et SQL PAAS
SQL Server WA SQL Database
(IaaS) (PaaS)
Développement Migration d’applications Nouvelles applications
Management Contrôle complet Service géré
Compatibilité Toutes les fonctionnalités SQL Basé sur les technologies SQL
• Transport Réseau (Tabular Data Stream)
• LangageSQL (Transact-SQL)
• APIs d’accèsaux données(ADO.NET, ODBC, JDBC)
• Outilsde développement(SQL Server Data Tools)
• Outilsde gestion(SQL Server Management Studio)
7. Fonctionnalités non incluses
SQL Server WA SQL Database
(IaaS) (PaaS)
SQL Haute Disponibilité Master Data Services
SQL Azure Sync CDC
Federations Data Compression
Impor Export Service Extended Events
Maintenance complet CLR
Management REST API Filestream
iFTS
Toutes les fonctionnalités SQL Performance Data Collector
Resource Governor
SQL Server Replication
TDE
Database Mirroring
9. Migration vers la plateforme IAAS
• Version supportées
– SQL SERVER 2012, 2008 R2, 2008
• Fonctionnalités
– Toutes les fonctionnalités excepté le Failover Cluster
• Installation
– Création à la volée d’une machine virtuelle SQL SERVER
– Téléchargement de votre propre VM
• License
– Paiement à l’heure.
– Migration de votre licence via la Software Assurance
10. Machines virtuelles et Editions SQL
Bande
VM Size CPU Coeurs Mémoire Disques Edition SQL
passante
Extra Small Partagé 768 MB 5 (Mbps) 1 Express
Small 1 1.75 GB 100 (Mbps) 2 Standard
Medium 2 3.5 GB 200 (Mbps) 4 Standard
Standard /
Large 4 7 GB 400 (Mbps) 8
Enterprise
Standard /
Extra Large 8 14 GB 800 (Mbps) 16
Enterprise
11. Créer une machine virtuelle SQL SERVER sur AZURE
SQL SERVER MODE IAAS
14. SQL AZURE DATABASE
• SQL SERVER en tant que
Service
• Autonome
• Support automatique du
mode HA (et c’est gratuit)
• Scalable (Fédérations)
• Idéal pour l’encapsulation
du management d’un
serveur
15. Pare-Feu SQL AZURE DATABASE
• Sécuriser vos données
• Contrôle d’accès en fonction de l’adresse IP
• Règles au niveau du serveur ou de la base de
données
• Aucune adresse IP autorisée par défaut
• Configurable via le portail, API REST ou T-SQL
• Option pour les autorisations inter AZURE
16. Serveur
• Création d’un
serveur depuis le
portail Azure
• Automatisation
possible via des
api REST ou des
scripts
Powershell
17. Connexion
<connectionStrings>
<addname="AdventureWorks"connectionString=
"Data Source=[server].database.windows.net;
• Depuis SSMS Integrated Security=False;
Initial Catalog=ProductsDb;
User Id=[login];
Password=[password];
Trusted_Connection=False;
• Depuis SSDT
Encrypt=true;"
providerName="System.Data.SqlClient"/>
</connectionStrings>
21. FEDERATIONS
• Etablir un scaling de base
via la communication multi-
nœuds
• Les données sont
garanties, quelque soit le
nœud attaqué
• Ajout et suppression de
nœud « à la volée »
• Syntaxe SQL nouvelle
• Partition dynamique sans
arrêt de service
25. SQL Data Sync
• Adaptable
– Le service d’adapte suivant
la demande en ressources
• Pas de code de configuration
– Toutes les données à définir
sont choisies via un assistant
• Planificateur de synchronisation
– Choisissez une planification de synchronisation
• Gestion des conflits
– Permet de capturer les problèmes de modification d’une même donnée à plusieurs endroits
• Logging et Monitoring
– SQL Data Sync permet une administration efficace de trace et de monitoring des éventuels problèmes
29. SQL vs NoSQL vs Hadoop (MapReduce)
Feature SQL NoSQL Hadoop
Grand stockage(PB)
Grand traitement (PB)
Tolérance aux pannes facile
Réplication facile
Mise en échelle linéaire
Pseudo – SQL
Faible Latence
Strong consistency (ACID)
30. Hadoop : 10 ans d’histoire
Aujourd’ui
2003 2008
• 10.000 Nodes
• Map/Reduce • Record Sort • Cluster on
1TB 209 sec demand
• Google File
• Entreprise ready
System
2006 2012
• Hadoop • Biggest Cluster
• Open Source • 100PB +0,5p/d
• Java
31. Accès à HDInsight
Azure BLOB Storage
Data IN
Hadoop
Jscript Console
Local batch
Traitement C# Streaming Map
JScript Console Pig / Hive Reduce
Hive ODBC Hive Jobs HDFS
Azure
Hive ODBC
Blob
Azure BLOB Storage
Data Out Storage
Scoop
34. Une application à 1 PB
SSRS
Web Role
Cluster
SSAS
SQL Server Azure Table Storage HDInsight
35. Un exemple NOAA.gov
FTP
Web Role Worker Role
Azure Table Storage HDInsight
36.
37. Donnez votre avis !
Depuis votre smartphone, sur :
http://notes.mstechdays.fr
De nombreux lots à gagner toutes les heures !!!
Claviers, souris et jeux Microsoft…
Merci de nous aider à améliorer les TechDays
http://notes.mstechdays.fr
38. Développeurs Pros de l’IT
http://aka.ms/generation-app Formez-vous en ligne www.microsoftvirtualacademy.com
http://aka.ms/evenements-
developpeurs Retrouvez nos évènements http://aka.ms/itcamps-france
Les accélérateurs
Faites-vous accompagner
Windows Azure, Windows Phone,
gratuitement
Windows 8
Essayer gratuitement nos http://aka.ms/telechargements
solutions IT
La Dev’Team sur MSDN Retrouver nos experts L’IT Team sur TechNet
http://aka.ms/devteam Microsoft http://aka.ms/itteam
Hinweis der Redaktion
Intro code / dev
Slide Objectives:Explain the three established terms in the industry for cloud servicesSpeaker Notes:There is a lot of talk in the industry about different terms like Platform as a Service, Infrastructure as a Service, and Software as a Service.Since PDC08 when we first announced the Windows Azure our focus has been on delivering a platform as a service offering where you can build applications. Where the platform abstracts you from the complexities of building and running applications. We fundamentally believe that the future path forward for development is by providing a platform. In fact, as you’ll see in a few minutes, we believe that there are a number of new capabilities that should be delivered as services to the platform.Notes:There is a lot of confusion in the industry when it comes to the cloud. It’s important that you understand both what is happening in the industry and how we think about the cloud. This is the most commonly used taxonomy for differentiating between types of cloud services.The industry has defined three categories of services:IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications. PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed. SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue. It is important to note that these 3 types of services may exist independently of one another or combined with one another. SaaS offerings needn’t be developed upon PaaS offerings although solutions built on PaaS offerings are often delivered as SaaS. PaaS offerings also needn’t expose IaaS and there’s more to PaaS than just running platforms on IaaS.
Speaker Notes:One of the other things we do with Windows Azure to enable that is provide a bunch of Application Building BlocksThese are managed services that we run that provide a lot of value so you can avoid standing up the infrastructure for common capabilitiesYou always can stand up VMs and put anything you want in itBut in a lot of cases you will find that we have built in services that we deliver or that are delivered by our partnersWhat’s cool is that you can use any of these services with a VM, with a Web Site, or with a Cloud Service – so you have flexibility in how you will consume them.
Slide Objectives:Understand that while there are physical SQL Server boxes behind the scenes, when connecting to SQL Database, you are not connecting to a physical server, but to a TDS endpoint.Transition:The key to understanding SQL Database is understanding while SQL Database is SQL Server, we do not interact with them in the same physical manner. Speaking Points:In an on-premises environment, we typically have physical access to the actual SQL Server server.In Windows Azure, we do not have physical access to the actual server.Notes:It is important that the attendee understands that it IS INDEED SQL Server at the platform layer. There are physical boxes running SQL Server 2012 Enterprise Edition. However, due to the nature of the Azure environment to provide the high-availability and scalability necessary, access to the physical boxes is currently not supported.
Slide Objectives:Illustrate the how SQL Database Firewall Transition:Transition statement(s) to setup the slideSpeaking Points:By default, no-one is allowed to access the database.Server Rules enable clients to access your entire SQL Database serverDatabase rules enable clients to access individual databases within your SQL Database serverRules are originating IP Address-based.Notes:Maximum of 128 RulesRather than using a REST API like the other Azure storage services, SQL Database is accessed via Tabular Data Stream (TDS), the same protocol used by Microsoft SQL Server (operating over port TCP/1433). To help protect thedata, the SQL Database firewall prevents all access to your SQL Database server until you specify which computers have permission. Initially, all access to your SQL Database server is blocked by the SQL Database firewall; connection attempts originating from the Internet or Windows Azure will not be able to reach your SQL Database server. In order to begin using your SQL Database server, you must go to the SQL Database Portal and specify one or more firewall settings that enable access to your SQL Database server. Use the firewall settings to specify which IP address ranges from the Internet are allowed, and whether or not Windows Azure applications can attempt to connect to your SQL Database server.
Notation
Exemple de page de code pour le secteur dev
Les blocs de couleurs sont éditables et peuvent reprendre la couleur du type de session qui est donnée.