SQL Azure

SQL Azure is Microsoft's RDBMS for the cloud. This course shows how to use SQL Azure for applications that live in your department, in your datacenter, and in the cloud.
Course info
Rating
(156)
Level
Intermediate
Updated
Jan 24, 2011
Duration
2h 38m
Table of contents
Description
Course info
Rating
(156)
Level
Intermediate
Updated
Jan 24, 2011
Duration
2h 38m
Description

SQL Azure is Microsoft's RDBMS for the cloud. Because it is based on SQL Server, developers can apply what they know about SQL Server to SQL Azure immediately. SQL Azure is its own product and, over time, developers will discover that they need to know some extra items in order to be fully productive on this platform. This module covers much of what developers need to know: basic development, security models, integration with existing platforms, and pricing. It covers new features like the SQL Azure OData service as well.

About the author
About the author

Scott Seely is the president of The Jeanius Factory, Inc., a Microsoft Regional Director and a Microsoft MVP.

More from the author
Building Windows Runtime Components
Intermediate
1h 23m
May 30, 2013
Migrating Internet Applications to Azure
Intermediate
2h 0m
Nov 1, 2012
Microsoft Azure Service Bus
Intermediate
2h 5m
Jan 9, 2012
More courses by Scott Seely
Section Introduction Transcripts
Section Introduction Transcripts

SQL Azure Overview
Hi, my name is Scott Seely and I'm with Pluralsight. In this module, we're going to take a look at what is SQL Azure. In this introductory overview module what we're going to do is we're going to try to give you a sense of what SQL Azure actually is. Now what you may know is that SQL Azure is a cloud based deployment of SQL Server. What we're going to start off in the module then is a very basic overview of some o f the different technologies that are at play whenever you're using SQL Azure. We start out by looking at what the actual product is. We then move over and take a look at the architecture of SQL Azure and understand the various pieces that make up any SQL Azure implementation. With our database then, one of the things we'll want to be concerned about is security. Who can access our SQL Azure implementation? So what we will also do is look at SQL Azure security. And finally, we'll do a little bit of a comparison between SQL Azure and SQL server, so you have an understanding of the capabilities that are available in SQL Azure, the capabilities that are available in SQL Server and what the delta between the two is.

SQL Azure Pricing
Hi, my name is Scott Seely, and I'm with Pluralsight. Let's get ready to understand SQL Azure pricing. There's a new type of cost in your applications, monetary cost. Typically when we're developing applications, we developers worry about things like, memory cost, disk space cost, time cost. Well with SQL Azure, you know with the cloud in general, we have a new cost that we always have to be aware of which is, every time we make a decision. We have to be aware, that we're adding to actual ongoing operational costs for our applications. Now, adding operational costs for applications shouldn't be a scary thing. As a matter of fact our applications have always had operational costs, but these costs have been hidden. We don't think about personnel costs. We don't think about costs for running the server or added electricity. Those costs are always handled by somebody else. However now when we develop an application, we can directly trace the $10 a month that we spend on SQL Azure, back to our one application. So with that in mind, what we're going to do is we're going to make you the developer aware of the costs you have, when you're using SQL Azure. We're going to start up by looking at SQL Azure pricing to understand how much each unit costs. We'll then do a brief overview so you can understand how a SQL Azure bill is constructed, and what it looks like when you're reading things. And finally, I'm going to bring up one of my own SQL Azure bills, just to show you what the detail items look like. Now because it's a SQL Azure bill that I use on this development account, there's not going to be a lot of lines in there, but there is enough detail in there that should be able to show you, how to read the actual bill.

Developing for SQL Azure
Hi, My name is Scott Seely, and I'm with Pluralsight. In this module, we're going to talk about developing applications for SQL Azure. As an application developer, one of the things I've grown to love about SQL Azure is that I can treat it as just yet another version of SQL Server. With that in mind, what we're going to do in this module. Is take a look at how do you develop applications for SQL Azure knowing that for the most part this is just yet another version of SQL Server. So we'll start out by taking a look at how do you pick a candidate application. When you develop against SQL Azure you want to make sure you're successful. Picking the right candidate application whether for transition or for brand new development. Will be key if your having some success with the platform. We'll then talk with the deployment architecture and how you move applications into the cloud. One of the considerations you're going to have as a developer are what are the set of tools that you have available to you when you're creating your solutions. So we'll briefly look at the tools as well. And finally we'll take a look at using SQL Azure with ADO. NET and entity framework, after all we are developers and we're going to be using the existing tools in order to develop our applications.

Migrating Data to SQL Azure
Hi my name is Scott Seely and I'm with Pluralsight. In this module we're going to talk about moving data from other databases into SQL Azure. One of the things that can strike fear into the heart of a developer is say hey we're going to do a data migration from our existing technology over to something that's brand new. What we want to do in this module is we want to take out a lot of that fear and anxiety that comes with doing a data migration. So we're going to look at just what you need to think about what types of data can move around and so on. So we'll start of by saying, hey what kind of data actually can move to SQL Azure? You'd be surprised what can work here. Pretty much any relational database management system you can think of can go from wherever your housing things over to SQL Azure. We'll then talk about how do you prepare for the move. What are the steps you need to do ahead of time, what sort of planning you need to do, and whats the testing you need to do once that move is complete. We'll spend a little bit of time talking about the difficulty evaluation. What types of moves are going to be easier than others. Or more difficult, more challenging than others. And along the way we'll talk about a lot of the tools that are available to you as a developer to make the migration easier. Or at least to make the migration more comprehensible and easier to plan out.

Using the SQL Azure OData Service
Hi, my name is Scott Seely and I'm with Pluralsight. In this module, we're going to talk about using the SQL Azure OData Service. Please keep in mind, that all the content in this module, is based on a community technology preview. As such things are subject to change, as a technology preview is iterated on and new versions ship. Most interesting applications gather and store data in some way. In order to make that data even more useful, a lot of times those applications have requirements to also expose that data to outside consumers. One of the things you can do is you can create your own, custom data consumption protocol, or you could use something like OData, which is a standard that's been pushed by Microsoft and other industry vendors, over the last few years. If you have a SQL Azure database, one of the things that Microsoft thought would be very interesting for you, is to be able to take data that you have stored and expose that data to the outside world. To help understand how that all works out, we're going to start out, with an introduction to what OData is. Once we understand what OData is, what the protocol is and how it works, we'll then take a look at how OData and SQL Azure interact. Of course when you go to exposing data to the outside world you going to want to figure out, how can you make sure that people who can read my data, can't also go back and update that same data? So we'll close out by looking at some ways to secure your OData.

SQL Azure and Business Intelligence
Hi, my name is Scott Seely and I'm with Pluralsight. This module, we are going to talk about SQL Azure with Business Intelligence solutions. As developers, its always very tempting to go out and use the latest new tools without thinking what it means for the business overall. Did I take away some features that the business needs? Have I hurt the business in some way? Instead, what we're trying to think about are ways that we can accomplish our goals more effectively. When it comes time to explain how SQL Azure's going to fit into your overall business, one area you can't neglect is business intelligence. Whether or not you're familiar with business intelligence, you need to know that the data gathering of your company is very important for decision makers to make sure that their doing the right things. And also to make sure they stop doing the wrong thing. So that you have some understanding of what business intelligence is and why its used, we'll do a little primer on what business intelligence is from the 60, 000 foot level. We'll then take a brief look at the tools that folks using business intelligence. Whenever you see someone cracking out a spreadsheet or digging into a report, you might wonder why are they doing this? Why do they spend all their days on these tools? To them, these tools are as important to their jobs as visual studio is to your job. So look at the tools that are being used in BI, so you can understand how things integrate. And then we'll go through some demos showing how easy it is to take a SQL Azure database and use the existing tools to generate the information that people need. This way when you go ahead and you say, we should do our next database using SQL Azure because of a number of cost savings or just performance reasons or something else. You can also assure all the folks who live in Excel or live in Reports that the choice to go to SQL Azure leaves all their current analysis options open.