SQL Azure The Breakfast of DBA Champions

1. SQL Azure The Breakfast of DBA Champions

2. How familiar are you with SQL Azure? Never used it Somewhat Expert Never used it � Maybe heard of it or read an article about it. Somewhat � Created a WA account, SA server and database. Connected to the database and performed some basic operations. Wrote a quick Hello World app in WA that used SQL Azure. Expert � Developed/Supported or worked with SQL Azure for a larger scale production application. Troubleshoot SQL Azure issues related to that application. Never used it � Maybe heard of it or read an article about it. Somewhat � Created a WA account, SA server and database. Connected to the database and performed some basic operations. Wrote a quick Hello World app in WA that used SQL Azure. Expert � Developed/Supported or worked with SQL Azure for a larger scale production application. Troubleshoot SQL Azure issues related to that application.

3. Agenda SQL Azure Database Overview SQL Azure Data Sync Overview App Admin Role definition Administering SQL Azure

4. Overview

5. Windows Azure Platform Slide ObjectiveUse this slide to transition show an overview of the Windows Azure platform and show that SQL Azure is part of a larger platform that offers a set of related services. Speaker Notes Introduce SQL Azure as part of Microsoft�s Cloud Platform Explain that Windows Azure is Microsoft�s cloud (PaaS) solution and SQL Azure is the DB part of that solution. Introduce some of the other related WA services. When SQL Azure section expands, talk to the key platform capabilities provided by SQL Azure (Database, Reporting and DataSync) Explain that this is an open platform that works with many different languages and tools, not just VS. These capabilities and why and how we developed them will be covered in subsequent slides. Slide ObjectiveUse this slide to transition show an overview of the Windows Azure platform and show that SQL Azure is part of a larger platform that offers a set of related services. Speaker Notes Introduce SQL Azure as part of Microsoft�s Cloud Platform Explain that Windows Azure is Microsoft�s cloud (PaaS) solution and SQL Azure is the DB part of that solution. Introduce some of the other related WA services. When SQL Azure section expands, talk to the key platform capabilities provided by SQL Azure (Database, Reporting and DataSync) Explain that this is an open platform that works with many different languages and tools, not just VS. These capabilities and why and how we developed them will be covered in subsequent slides.

6. SQL Azure Database Familiar SQL Server relational model Support existing APIs and tools Friction free provision and reduced management Built for the cloud with availability, scale, pay as you go model Slide Objective This slide captures the high level value props. of SA database public service. Speaker Notes Familiar � On the surface it looks and feels just like SQL Server. Agility � Key value prop. You can easily go to a website provision a DB, use an existing client library to connect to it and start programming against that DB and you can do all this very quickly. Can build applications that deliver new capabilities to the users of the apps without having to build our multiple DCs around the world. Both of those value props are key for developer agility and for using SQL Azure today. Self-Managing � Conceptually separate the HW infrastructure and low level instance maintenance, those types of operations are done by the service itself. The service does that on behalf of the tenants. You are able to easily and quickly create DBs and focus on dealing with the higher level DB administration, app. administration, higher value type of maintenance. Do not need to worry about HW setup and HA setup and so forth. Elastic Scale � As a broad service we provide elastic scale. We have 100s and even 1000s of machines around the world in our DCs. You create a couple or 100s of DBs and you do not worry about the right number of DBs in the right locations with the right cooling and so forth. You do not worry about those types of issues that limit this type of scale. You create more databases are needed and do not worry about the HW aspects relating to scale. Slide Objective This slide captures the high level value props. of SA database public service. Speaker Notes Familiar � On the surface it looks and feels just like SQL Server. Agility � Key value prop. You can easily go to a website provision a DB, use an existing client library to connect to it and start programming against that DB and you can do all this very quickly. Can build applications that deliver new capabilities to the users of the apps without having to build our multiple DCs around the world. Both of those value props are key for developer agility and for using SQL Azure today. Self-Managing � Conceptually separate the HW infrastructure and low level instance maintenance, those types of operations are done by the service itself. The service does that on behalf of the tenants. You are able to easily and quickly create DBs and focus on dealing with the higher level DB administration, app. administration, higher value type of maintenance. Do not need to worry about HW setup and HA setup and so forth. Elastic Scale � As a broad service we provide elastic scale. We have 100s and even 1000s of machines around the world in our DCs. You create a couple or 100s of DBs and you do not worry about the right number of DBs in the right locations with the right cooling and so forth. You do not worry about those types of issues that limit this type of scale. You create more databases are needed and do not worry about the HW aspects relating to scale.

7. SQL Azure Database Cloud relational database based on SQL Server engine Use same tools, data access frameworks, T-SQL based language Global datacenters High Availability & Redundancy Reads are completed at the primary Writes are replicated to a quorum of secondaries Slide ObjectiveUse this slide to transition into an explanation of SQL Azure Database (Reporting and Data Sync will be covered later) Explain at a high level how SQL Azure works Speaker Notes Design Principle of SQL Azure: Focus on combining the best features of SQL Server running at scale with low friction SQL Azure is a high availability database Always three transaction consistent replicas of the database One primary replica; two slave replicas Failure of a replica will result in another replica being spun up immediately by the fabric Failure of the primary replica means a slave replica will become the primary and a new slave will spin up Minimal down time Typically just a few dropped connections Easy to code for the failover scenario Clustered index required on all tables to allow replication Notes Useful article from SQL Azure team http://msdn.microsoft.com/en-us/magazine/ee321567.aspx Slide ObjectiveUse this slide to transition into an explanation of SQL Azure Database (Reporting and Data Sync will be covered later) Explain at a high level how SQL Azure works Speaker Notes Design Principle of SQL Azure: Focus on combining the best features of SQL Server running at scale with low friction SQL Azure is a high availability database Always three transaction consistent replicas of the database One primary replica; two slave replicas Failure of a replica will result in another replica being spun up immediately by the fabric Failure of the primary replica means a slave replica will become the primary and a new slave will spin up Minimal down time Typically just a few dropped connections Easy to code for the failover scenario Clustered index required on all tables to allow replication Notes Useful article from SQL Azure team http://msdn.microsoft.com/en-us/magazine/ee321567.aspx

8. Slide Objective Drilling into a bit more what happens in the DC. The goal of this slide is to provide as much info as possible as to what goes in a DC. The idea is that the more you know about the system the better you can leverage it. Speaker Notes There is a lot of detail, but there are a few key points I�d like for you to take away from here. 1. Your application talks to SQL Azure across the internet to a TDS endpoint. Logically the DC presents a TDS endpoint for your application to connect to and through that endpoint you interact with SQL Azure. This allows us to re-use the same client libraries and existing tooling for SQL Server. Enforced SSL encryption. 2. When you connect to your database you don�t actually connect to the SQL boxes but to one of the GW boxes Your request is routed through the GW tier. GW is the thing that authenticates you when you log into your server. Will look up in the metadata where in the backend your database is. Also provides that concept of a logical database over the shared infrastructure. For example when you create DB, the call is intercepted by the GW and ensures that the DB is created as well as replicas of the DB which are kept in sync and which of course gives us fault tolerance in the system such that if we loose a copy we can switch over to using one of the secondary copies as the primary and rebuild another secondary copy. The fact that you don�t see any of that is because all that work is done by the GW tier. 3. At the bottom the SQL boxes are basically core relational engine SQL Server (with some modifications for the cloud) boxes running on commodity hardware. At the very bottom, the fabric layer is the software that to enable all of those nodes to work together and co-operate. To monitor hardware failures, software errors and take the needed actions to respond to those errors to make sure the system stays available and your data is maintained. This technology allows us to failover in a matter of seconds when a node with your primary data fails. Also responsible for load balancing across the entire cluster and a single node. Slide Objective Drilling into a bit more what happens in the DC. The goal of this slide is to provide as much info as possible as to what goes in a DC. The idea is that the more you know about the system the better you can leverage it. Speaker Notes There is a lot of detail, but there are a few key points I�d like for you to take away from here. 1. Your application talks to SQL Azure across the internet to a TDS endpoint. Logically the DC presents a TDS endpoint for your application to connect to and through that endpoint you interact with SQL Azure. This allows us to re-use the same client libraries and existing tooling for SQL Server. Enforced SSL encryption. 2. When you connect to your database you don�t actually connect to the SQL boxes but to one of the GW boxes Your request is routed through the GW tier. GW is the thing that authenticates you when you log into your server. Will look up in the metadata where in the backend your database is. Also provides that concept of a logical database over the shared infrastructure. For example when you create DB, the call is intercepted by the GW and ensures that the DB is created as well as replicas of the DB which are kept in sync and which of course gives us fault tolerance in the system such that if we loose a copy we can switch over to using one of the secondary copies as the primary and rebuild another secondary copy. The fact that you don�t see any of that is because all that work is done by the GW tier. 3. At the bottom the SQL boxes are basically core relational engine SQL Server (with some modifications for the cloud) boxes running on commodity hardware. At the very bottom, the fabric layer is the software that to enable all of those nodes to work together and co-operate. To monitor hardware failures, software errors and take the needed actions to respond to those errors to make sure the system stays available and your data is maintained. This technology allows us to failover in a matter of seconds when a node with your primary data fails. Also responsible for load balancing across the entire cluster and a single node.

9. Service Provisioning Model Slide ObjectiveExplains the hierarchy of concepts around SQL Azure provisioning Speaker Notes Account is just a Windows Azure Platform account- common across Windows Azure, SQL Azure, Windows Azure AppFabric Billing occurs at the account level If building a SaaS type scenarios may want to either let customer provide their own account or DB or; May need to on-bill charges Servers are a purely logical concept Appears to TDS client like a SQL Server Is in fact just a fa�ade that routes requests to underlying data nodes Servers have an auto generated DNS name that is used to locate them Users authenticate at the server level (i.e. must be associated at the server level) more on Security on Day 3 A server is geo-located (either explicitly or via affinity group) Database is and appears to be a standard SQL Database Rich support for T-SQL constructs and SQL objects Database is the largest unit of transactional consistency;l There is no support for distributed transaction that span DBs Notes SQL Azure Provisioning Model http://msdn.microsoft.com/en-us/library/ee336227.aspxSlide ObjectiveExplains the hierarchy of concepts around SQL Azure provisioning Speaker Notes Account is just a Windows Azure Platform account- common across Windows Azure, SQL Azure, Windows Azure AppFabric Billing occurs at the account level If building a SaaS type scenarios may want to either let customer provide their own account or DB or; May need to on-bill charges Servers are a purely logical concept Appears to TDS client like a SQL Server Is in fact just a fa�ade that routes requests to underlying data nodes Servers have an auto generated DNS name that is used to locate them Users authenticate at the server level (i.e. must be associated at the server level) more on Security on Day 3 A server is geo-located (either explicitly or via affinity group) Database is and appears to be a standard SQL Database Rich support for T-SQL constructs and SQL objects Database is the largest unit of transactional consistency;l There is no support for distributed transaction that span DBs Notes SQL Azure Provisioning Model http://msdn.microsoft.com/en-us/library/ee336227.aspx

10. SQL Azure Data Sync Overview

11. SQL Azure Data Sync Slide Objective Give an overview of sync service scenarios and highlight the value props. Speaker Notes There are 4 main scenarios for sync service. Hybrid App Sync When you can�t migrate the entire app to the cloud you move a certain workload of the app to the cloud and leave the rest on prem. For example leave OLTP workload on prem and move the BI aspect of the app to the cloud. Branch offices Sync Multiple branch offices run an app. and you need to collect aggregated data about all the offices. You sync the required data from each of the remote offices to SQL Azure and do your analysis. Within SQL Azure, same datacenter You want to scale out within one DC and separate your workloads, for example OLTP and BI. Within SQL Azure, different datacenter You want your customers to have quick response times when using your application and you need to keep the data close to the app tier to avoid long latencies. Slide Objective Give an overview of sync service scenarios and highlight the value props. Speaker Notes There are 4 main scenarios for sync service. Hybrid App Sync When you can�t migrate the entire app to the cloud you move a certain workload of the app to the cloud and leave the rest on prem. For example leave OLTP workload on prem and move the BI aspect of the app to the cloud. Branch offices Sync Multiple branch offices run an app. and you need to collect aggregated data about all the offices. You sync the required data from each of the remote offices to SQL Azure and do your analysis. Within SQL Azure, same datacenter You want to scale out within one DC and separate your workloads, for example OLTP and BI. Within SQL Azure, different datacenter You want your customers to have quick response times when using your application and you need to keep the data close to the app tier to avoid long latencies.

12. SQL Azure Data Sync No-Code Sync Configuration Configure and manage using Windows Azure Portal Define data to be synchronized and locations Choose how often data is synchronized Specify optional filters Full Data Synchronization Capabilities Two-way sync of same data, as well as one-way sync Conflict Handling Detect and resolve conflicts caused by the same data being changed in multiple locations Slide Objective Highlight some of the key data sync service features. Speaker Notes All sync scenarios can be configured without the need to write any code. The service is capable of doing one way or 2-way sync with conflict resolution. Notes Data Sync links: http://www.microsoft.com/windowsazure/features/database/#data-sync http://blogs.msdn.com/b/sqlazure/archive/2011/06/13/10167419.aspx http://blogs.msdn.com/b/sqlazure/archive/2010/07/16/10039319.aspx http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/COS308 Microsoft Sync Framework links: http://msdn.microsoft.com/en-us/sync/default.aspx http://msdn.microsoft.com/en-us/library/bb902854(v=SQL.110).aspx http://blogs.msdn.com/b/sync/Slide Objective Highlight some of the key data sync service features. Speaker Notes All sync scenarios can be configured without the need to write any code. The service is capable of doing one way or 2-way sync with conflict resolution. Notes Data Sync links: http://www.microsoft.com/windowsazure/features/database/#data-sync http://blogs.msdn.com/b/sqlazure/archive/2011/06/13/10167419.aspx http://blogs.msdn.com/b/sqlazure/archive/2010/07/16/10039319.aspx http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/COS308 Microsoft Sync Framework links: http://msdn.microsoft.com/en-us/sync/default.aspx http://msdn.microsoft.com/en-us/library/bb902854(v=SQL.110).aspx http://blogs.msdn.com/b/sync/

13. App Admin Role

14. Who is the App Admin? Slide Objective Explain who is the app admin for each customer type. Key takeaway is that it may be more than one person performing the job. The 2nd key takeaway is that for Cloud Service Vendors (CSVs) the app admin must perform the job in a highly automated fashion because they have to scale to millions of users and potential this could mean millions of DBs. Speaker Notes Who performs the app admin role depends on the customer type. 1. Breath/Web, SMB, Departmental Usually a single person supports both the app and data tier. They usually support 1 to 10 apps each having a single fairly small DB. 2. Tier 1 These apps are mission critical and have dedicated people for both the application tier and data tier. The admins are experts in their area and the apps are closely monitored and managed by the admins. These folks usually do not support multiple Tier 1 apps. 3. CSV Cloud service vendor is a company that sells SaaS applications to customers They operate a service and need to be able to monitor and troubleshoot that service. The service may have millions of customers which may result in millions of DBs to manage. The service is usually managed by many folks, and there is no traditional app admin like in the other 2 segments. The app admins here must do things differently from 1 & 2 since they must deal with such large scale they have to perform the management operations in a way that allows them to deal with such large scale. Slide Objective Explain who is the app admin for each customer type. Key takeaway is that it may be more than one person performing the job. The 2nd key takeaway is that for Cloud Service Vendors (CSVs) the app admin must perform the job in a highly automated fashion because they have to scale to millions of users and potential this could mean millions of DBs. Speaker Notes Who performs the app admin role depends on the customer type. 1. Breath/Web, SMB, Departmental Usually a single person supports both the app and data tier. They usually support 1 to 10 apps each having a single fairly small DB. 2. Tier 1 These apps are mission critical and have dedicated people for both the application tier and data tier. The admins are experts in their area and the apps are closely monitored and managed by the admins. These folks usually do not support multiple Tier 1 apps. 3. CSV Cloud service vendor is a company that sells SaaS applications to customers They operate a service and need to be able to monitor and troubleshoot that service. The service may have millions of customers which may result in millions of DBs to manage. The service is usually managed by many folks, and there is no traditional app admin like in the other 2 segments. The app admins here must do things differently from 1 & 2 since they must deal with such large scale they have to perform the management operations in a way that allows them to deal with such large scale.

15. App Admin Responsibilities Slide Objective Give an overview of what types of tasks the app admin is responsible for. Also explain how these tasks may be performed differently in the cloud then on-prem and this may require additional skills and a role change for the app admin. Speaker Notes The types of tasks in each of the 4 buckets may not be that different for on-prem. SQL Server. What is different is how these tasks may be performed for existing and new applications. The cloud introduces a Paradigm shift & Role change for the App Admin Manageability of small applications is different App Isolation also scopes its manageability Manageability of large scale SaaS applications is very different Acquire new skills to manage Sharding / TSO based or custom New Apps New concerns of cloud applications TCO - Operating costs analysis and tradeoffs between perf. vs. costSlide Objective Give an overview of what types of tasks the app admin is responsible for. Also explain how these tasks may be performed differently in the cloud then on-prem and this may require additional skills and a role change for the app admin. Speaker Notes The types of tasks in each of the 4 buckets may not be that different for on-prem. SQL Server. What is different is how these tasks may be performed for existing and new applications. The cloud introduces a Paradigm shift & Role change for the App Admin Manageability of small applications is different App Isolation also scopes its manageability Manageability of large scale SaaS applications is very different Acquire new skills to manage Sharding / TSO based or custom New Apps New concerns of cloud applications TCO - Operating costs analysis and tradeoffs between perf. vs. cost

16. Administering SQL Azure Database

17. Logical vs. Physical Administration SQL Azure focus on logical administration Schema creation and management Query optimization Security management (Logins, Users, Roles) Service handles physical management Automatically provides HA �out of box� Transparent failover in case of failure Load balancing of data to ensure SLA Slide ObjectiveProvides a guide to where SQL Azure customers need to provide administration Speaker Notes SQL Azure is targeted at logical config and admin only Crete schema and create indexes etc Optimize queries- can get query plan in SSMS etc.. Management of users and roles SQL Azure provides automatic physical management Automated failover Load balancing Cannot choose physical file locations- no way to spread file groups across spindles Partitioning is up to developers- done at the database level- each database is a partition Notes SQL Azure vs SQL Server differences http://www.microsoft.com/downloads/details.aspx?FamilyID=86f12b41-1eba-4567-9ac8-02eaa7d12034&displaylang=en Slide ObjectiveProvides a guide to where SQL Azure customers need to provide administration Speaker Notes SQL Azure is targeted at logical config and admin only Crete schema and create indexes etc Optimize queries- can get query plan in SSMS etc.. Management of users and roles SQL Azure provides automatic physical management Automated failover Load balancing Cannot choose physical file locations- no way to spread file groups across spindles Partitioning is up to developers- done at the database level- each database is a partition Notes SQL Azure vs SQL Server differences http://www.microsoft.com/downloads/details.aspx?FamilyID=86f12b41-1eba-4567-9ac8-02eaa7d12034&displaylang=en

18. Programming Surface Area Current Tables, indexes and views Stored Procedures Triggers Constraints Table variables, session temp tables Spatial Collation � Future Full Text Search Windows Auth. CLR Service Broker Distributed Txn/Query Never Physical server views File groups File Stream Slide ObjectiveProvides an overview of what features are supported in SQL Azure today. Speaker Notes Lots of the expected SQL Server features are available in SQL Azure today. Some that are not there yet will be available in the future. There are certain features which will never appear in SQL Azure because they deal with low level HW or instance management and now SQL Azure takes care of that for you. Notes http://msdn.microsoft.com/en-us/library/windowsazure/ee336250.aspx Slide ObjectiveProvides an overview of what features are supported in SQL Azure today. Speaker Notes Lots of the expected SQL Server features are available in SQL Azure today. Some that are not there yet will be available in the future. There are certain features which will never appear in SQL Azure because they deal with low level HW or instance management and now SQL Azure takes care of that for you. Notes http://msdn.microsoft.com/en-us/library/windowsazure/ee336250.aspx

19. Connection Model SQL Azure exposes native SQL Server TDS protocol Use existing client libraries ADO.NET, ODBC, JDBC, PHP Client libraries pre-installed in Windows Azure roles Support for ASP.NET controls Clients connect directly to a database Cannot hop across DBs (no USE) Slide ObjectiveProvides an overview of connectivity to SQL Azure and how basically it is similar to SQL Server. Speaker Notes SQL Azure uses the TDS (tabular data stream) protocol Very broad support for existing SQL Server tools Some things like backup tools and low level file manipulation tools will not work SQL Server client libraries available in Windows Azure Compute Very easy to connect to SQL Azure from Windows Azure SQL Azure is an ideal backing store for a Windows Azure application All of the ASP.NET controls are supported RAD in Visual Studio is simple with SQL Azure Each SQL Azure server is logical only Prevents DB context hopping No ability to USE DB_Foo Notes Useful article from SQL Azure team http://msdn.microsoft.com/en-us/magazine/ee321567.aspx Tooling support for SQL Azure Database http://msdn.microsoft.com/en-us/library/ee621784.aspx Slide ObjectiveProvides an overview of connectivity to SQL Azure and how basically it is similar to SQL Server. Speaker Notes SQL Azure uses the TDS (tabular data stream) protocol Very broad support for existing SQL Server tools Some things like backup tools and low level file manipulation tools will not work SQL Server client libraries available in Windows Azure Compute Very easy to connect to SQL Azure from Windows Azure SQL Azure is an ideal backing store for a Windows Azure application All of the ASP.NET controls are supported RAD in Visual Studio is simple with SQL Azure Each SQL Azure server is logical only Prevents DB context hopping No ability to USE DB_Foo Notes Useful article from SQL Azure team http://msdn.microsoft.com/en-us/magazine/ee321567.aspx Tooling support for SQL Azure Database http://msdn.microsoft.com/en-us/library/ee621784.aspx

20. Deployment Deploy via T-SQL scripts Support for SQL Server Data-Tier Applications (DAC) feature DACPAC is unit of deployment Cloud or on-premise is a deployment time choice Create Logical Server in same region as Windows Azure Affinity Group for code-near architecture Slide ObjectiveProvides a guide to deploying databases into SQL Azure Speaker Notes Typically use a SQL Script to create schema Use SSIS or a script to get data into SQL Azure Cannot attach database files- no place to put the file to attach No support for native SQL Server backup yet � coming soon. Ensure that Database is collocated with Windows Azure Compute Important to improve performance and prevent high traffic charges Can deploy Visual Studio DACPACs Data Access Collection Packages Notes Data Tier Applicationshttp://msdn.microsoft.com/en-us/library/ee240739.aspx http://msdn.microsoft.com/en-us/library/ee621784.aspx#ssis Slide ObjectiveProvides a guide to deploying databases into SQL Azure Speaker Notes Typically use a SQL Script to create schema Use SSIS or a script to get data into SQL Azure Cannot attach database files- no place to put the file to attach No support for native SQL Server backup yet � coming soon. Ensure that Database is collocated with Windows Azure Compute Important to improve performance and prevent high traffic charges Can deploy Visual Studio DACPACs Data Access Collection Packages Notes Data Tier Applicationshttp://msdn.microsoft.com/en-us/library/ee240739.aspx http://msdn.microsoft.com/en-us/library/ee621784.aspx#ssis

21. Database Migration Slide Objective Explain how we think about application health and what is supported today and in the future. Speaker Notes SQL Server Migration Assistant is a good tool to use if you�re migrating from non-SQL Server DB to SQL Azure. http://www.microsoft.com/en-us/showcase/details.aspx?uuid=d4a37bbc-9f85-40d5-91ef-d9ecb3b13d12 Generate Script Wizard tools is a great tools built into SSMS with native SQL Azure support that can generate a script for both schema and data. You can modify that script and then execute it to load the schema and data to SQL Azure. http://social.technet.microsoft.com/wiki/contents/articles/sql-azure-data-migration-using-sql-server-import-and-export-wizard.aspx Not the best tool for moving large amount of data. DACPAC/BACPAC What to manage end to end the lifecycle of your schema. http://msdn.microsoft.com/en-us/library/ee240739.aspx http://msdn.microsoft.com/en-us/library/ee621784.aspx#ssis SSIS/BCP Great tools to load large amounts of data into SQL Azure. Notes http://blogs.msdn.com/b/cbiyikoglu/archive/2010/06/10/migrating-applications-to-sql-azure-teched-2010-new-orleans.aspx http://msdn.microsoft.com/en-us/library/windowsazure/ee730904.aspx Slide Objective Explain how we think about application health and what is supported today and in the future. Speaker Notes SQL Server Migration Assistant is a good tool to use if you�re migrating from non-SQL Server DB to SQL Azure. http://www.microsoft.com/en-us/showcase/details.aspx?uuid=d4a37bbc-9f85-40d5-91ef-d9ecb3b13d12 Generate Script Wizard tools is a great tools built into SSMS with native SQL Azure support that can generate a script for both schema and data. You can modify that script and then execute it to load the schema and data to SQL Azure. http://social.technet.microsoft.com/wiki/contents/articles/sql-azure-data-migration-using-sql-server-import-and-export-wizard.aspx Not the best tool for moving large amount of data. DACPAC/BACPAC What to manage end to end the lifecycle of your schema. http://msdn.microsoft.com/en-us/library/ee240739.aspx http://msdn.microsoft.com/en-us/library/ee621784.aspx#ssis SSIS/BCP Great tools to load large amounts of data into SQL Azure. Notes http://blogs.msdn.com/b/cbiyikoglu/archive/2010/06/10/migrating-applications-to-sql-azure-teched-2010-new-orleans.aspx http://msdn.microsoft.com/en-us/library/windowsazure/ee730904.aspx

22. Application Health Today Live troubleshooting DMVs Historical troubleshooting Nothing Summaries and global view SQL Azure Portal Future Live troubleshooting Expanded DMV coverage Database Extended Events Historical troubleshooting Event Table (Logging) Long term trending Summaries and global view SQL Azure Portal integration Slide Objective Explain how we think about application health and what is supported today and in the future. Speaker Notes We break up app health into 2 main sections Live Troubleshooting � How do I troubleshoot issues in real time? Today we have few DMVs to help with that and in the future we will add additional DMVs to provide insight into the service. We will provide tracing for Performance, Workload capture, Health, etc. There is nothing like that today. Historical Troubleshooting � How do I monitor and understand the overall health of my application? There isn�t anything much today for historical troubleshooting. In the future we will provide you with an error log type feature similar to SQL Server and other long term storage of health data. Watch for product Designed for tracing � Performance, Workload capture, Health Slide Objective Explain how we think about application health and what is supported today and in the future. Speaker Notes We break up app health into 2 main sections Live Troubleshooting � How do I troubleshoot issues in real time? Today we have few DMVs to help with that and in the future we will add additional DMVs to provide insight into the service. We will provide tracing for Performance, Workload capture, Health, etc. There is nothing like that today. Historical Troubleshooting � How do I monitor and understand the overall health of my application? There isn�t anything much today for historical troubleshooting. In the future we will provide you with an error log type feature similar to SQL Server and other long term storage of health data. Watch for product Designed for tracing � Performance, Workload capture, Health

23. Security in SQL Azure Logical tenant isolation Encrypted communication Firewall rules to accept connections from specific IP addresses Uses regular SQL security model Authenticate logins, map to users and roles Authorize users and roles to SQL object Support for standard SQL Auth logins Username + password Slide ObjectiveOverview of SQL Azure security. Speaker Notes Mostly same as SQL Server, but there are a few minor differences. ALL connections are encrypted. You cannot connect to SQL Azure with an unencrypted connection. No support for Windows Auth., only SQL Auth. New to SQL Azure are logical server firewall rules Ability to define the set of IP address that can connect to the server. Key takeaway is that security model for SQL Azure is very similar to SQL Server. Users and logins are managed the same way as on-prem. SQL Server.Slide ObjectiveOverview of SQL Azure security. Speaker Notes Mostly same as SQL Server, but there are a few minor differences. ALL connections are encrypted. You cannot connect to SQL Azure with an unencrypted connection. No support for Windows Auth., only SQL Auth. New to SQL Azure are logical server firewall rules Ability to define the set of IP address that can connect to the server. Key takeaway is that security model for SQL Azure is very similar to SQL Server. Users and logins are managed the same way as on-prem. SQL Server.

24. Summary SQL Azure provides a highly available cloud database service. Managed service, scales on demand and facilitates faster innovation. Allows Admins to focus on high value administration. Introduces a paradigm shift with new responsibilities for Admins. Slide Objective Summarize key take away that SQL Azure does not remove the need for an app admin/DBA. It changes the role but does not replace it. Speaker Notes The service performs the lower level types of maintenance. This allows the admin to focus on higher value types of administration. It also introduces new things that requires the admins to take on additional responsibilities. Slide Objective Summarize key take away that SQL Azure does not remove the need for an app admin/DBA. It changes the role but does not replace it. Speaker Notes The service performs the lower level types of maintenance. This allows the admin to focus on higher value types of administration. It also introduces new things that requires the admins to take on additional responsibilities.

25. Try out SQL Azure and Windows Azure at: http://www.windowsazure.com/en-us/pricing/free-trial/ Try out SQL Azure and Windows Azure at: http://www.windowsazure.com/en-us/pricing/free-trial/