Dostupnost - data centri, redundantne kopije, automatski failover, load balancing Proširenje SQL Servera Manje konfiguracije i administracije, transparentni troškovi
Exposes a TDS (tabular data stream) Administracija na logickoj razini – korisnici, role, baze, indexi, statistike, optimizacija querya… fizičku administraciju radi MS -> SLA Fizički diskovi nisu dostupni, ne mogu se specificrati file grupe, podaci se automatski repliciraju pa backup i restore komande nisu primjenjive (nova verzija podrzava kopiranje u novu bazu) -> SSIS ili SQLCMD se mogu koristiti za bulk kopiranje Scenarij A: Bitno je paziti na network latency – minimizirati broj requestova!!!
Client - TDS interface, komunikacija sa SQL Azure, on-premise ili u Windows Azure Services - gateway između klijenta i platforme, billing, provisionining and routing Platform - fizički serveri i servisi (SQL Serveri), automatski failover, load balancing, replikacija, … health monitor Infrastructure – fizički hardver i OS
- SQL Azure server je logička grupa baza podataka, ponaša se kao centralna administracijska konzola za više baza - Svaki SQL Azure server ima FQDN, stvara se u procesu provisioninga: servername.database.windows.net - Read-only master DB se stvara automatski prilikom provisioninga (drži popis logina koji imaju prava stvarati nove baze ili loginove), pomoću nje se - mogu gledati usage metrics Prilikom provisioninga, SQL Azure kreira „sa” account (server-level principal), dodatni loginovi se mogu stvoriti na serveru SQL server logins (autentikacija), DB users (grant access at DB level), DB roles (group users, grant access)
Business edition – po 10 GB inkrement Moze se edicija mijenjati naknadno Naplacuje se i dodatni bandwith fee izvan platforme (transfer od-do klijenta ili između data centara) – paziti kod arhitekture rješenja
For example, you have a single Business Edition database that reached a peak size of 25 GB of data for one day. Using the 10 GB multiplier, a 25 GB Business Edition database would be equivalent to three 10 GB Business Edition databases for one month. To find the daily rate, divide by the average number of days in the month. Assuming a 30 day month, your daily data usage for that one day would be 1 GB of a Business Edition database, or (3 x 10 GB per month / 30 days per month) = 1 GB/day. Lets look at a few examples; Assume we have a a web edition database that has a MAXSIZE=5GB. If the database size is 800MB, the daily charge for the database will be at the 1GB rate for web edition. if the next day, the database size grows to 3GBs, the daily charge will be based on the next billing increment for web edition which is 5GB for that day. If the next day, after some data deletion, the size drops back to 900MB, the daily charge will be based on 1GB back again. The same example applies to a business edition edition database. Assume we have a business edition database with MAXSIZE=50GB. If the total database size is 8GB, the daily charge for the database will be at the 10GB rate. If the next day, the database size grows to 25GB, the daily charge will be based on the next billing increment for the business edition which is 30GB and so on. Account owner/administrator je glavni, on kupuje subscriptione na MS OSCP – subscriptioni se dodjeljuju service administratoru (mogu biti isti accounti), to je kao DBA ili dev Sys.database_usage – popis koristenja baza Sys.bandwidth_usage – opis bandwidtha za svaku bazu Velicina baze: podaci + indexi + objekti (ne ulaze logovi, system tables, master, server catalogs, …) Ako se napuni baza, više nema inserta/updatea ili stvaranja novih objekata – moze se citati, raditi dele, truncate, drop table/indeks, rebuild index
Administracija na razini baze je gotovo identična sa on-premise SQL Serverom Firewall – SQL Azure service samo na TCP 1433 (dovoljan je outbound), firewall settings se mora sloziti preko portala (IP range, Windows Azure konekcije) Sva komunikacija između SQL Azure DB i aplikacije se pod SSL-om SSMS i SQLCMD verzije prije 2008 R2 nisu podrzane (Express radi ok) Windows authentication (integrated security) nije (još) podržan, samo SQL authentication
Kopiranje baze u novu kao backup na serveru Sami se brinete o offline (on-premise) backupu Replikacija nije podržana
