I’ll be delivering a “Business Intelligence Landscape” session tonight at the UCSD Extension Continuing Education & Career Showcase. In talk I’ll go over what people mean when they say “Business Intelligence”, as well as some of the core concepts and common solutions. We’ll talk about stuff like Extract, Transform and Load (ETL), Data Warehouses, Star Schema, Cubes, Aggregates, MDX, KPIs Reporting Tools, and Data Mining. But if that weren’t enough we’ll see how the cloud and big data are changing the BI landscape as well.
Azure SQL Database “Premium” limited preview is now available. Premium edition databases offer performance advantages over the current Web and Business edition SQL Database offerings by allowing the reservation of a fixed amount of reserve capacity for a database, including it’s built-in secondary replicas. This ability is ideal for applications with requirements such as:
High Peak Load
Many Concurrent Requests
Currently, two “reservation sizes”, P1 & P2, are being offered. P1 offers better performance predictability than the current Web and Business editions, while P2 roughly doubles the performance of P1. Premium databases are billed based on their reservation size and storage volume.
If you are more of a “behind-the-scenes” kind of developer though, you may prefer to make your SQL tables using good old SSMS and some scripts. In short 5+ minute video below, I walk you through the steps and gotchas around creating tables directly in SQL Azure, but consuming them via Windows Azure Mobile Services.
As for the gotchas, there are two that come to mind:
Your tables must have a primary key column called “id”.
Your table names should be “singular” (think “Category” not “Categories”) to allow for more appropriate class names on the client side. You wouldn’t want to create a class called “Categories” when it really represents a single category.
If you want a copy of the SQL script I use in the video blow, you can get it here: http://aka.ms/wcts
It is easy to forget that an Azure SQL Database exists on an Azure SQL Server. One Azure SQL Server can support multiple Azure SQL Databases. The biggest benefit to a single Azure SQL Server hosting multiple databases is that you have a single administrative login and set of firewall rules that affect all databases on that server.
This can lead to confusion however if you have had a server in place for some time, and add a new database without remembering the original server credentials or firewall rules.
To remind yourself of the administrative login for your database, first login to the Azure Management Portal (https://manage.windowsazure.com). Along the left hand slide, select “SQL DATABASES”. On the “DATABASES” page, find your new database in the list, and locate the server name from the “SERVER” column (FYI, the real server names have been truncated in the screenshots below for security purposes):
If you click on the name of the server above, you will be taken to the “DASHBOARD” page for that server. From there, along the right hand side under “quick glance” you can see the “ADMINISTATOR LOGIN” name, and if needed click the link further up on the “Reset Administrator Password” link.
Once you have a figured out, or if needed reset, the administrator credentials. You can now log in an create additional logins and user accounts using the CREATE LOGIN and CREATE USER statements…
This is an awesome jam packed weekend for me. I had the Windows8 Dev Camp yesterday, and SQL Saturday 157 today. If you are a Database Professional (DBA or Dev) and don’t know about SQL Saturday’s, do your self a favor and find out about them! They are free (or extremely inexpensive) events held on Saturdays at locations all around the world. They are organized by local members of your community and supported by PAAS. If you don’t see a SQL Saturday in your region, maybe you could help get one organized!