Microsoft released SQL Azure more than two years ago - that's enough time for testing (I hope!). So, are you ready to move your data to the Cloud? If you’re considering a business (i.e. a production environment) in the Cloud, you need to think about methods for backing up your data, a backup plan for your data and, eventually, restoring with Red Gate Cloud Services. In this session, you’ll see the differences, functionality, restrictions, and opportunities in SQL Azure and On-Premise SQL Server 2008/2008 R2/2012. We’ll consider topics such as how to be prepared for backup and restore, and which parts of a cloud environment are most important: keys, triggers, indexes, prices, security, service level agreements, etc.

1. SQL Server in the CloudFrom Plan, To Backup, To Cloud
Tobiasz Janusz Koprowski | Independent Consultant

2. Our awesome sponsors

3. ABOUT ME
•Member of the Board Polish Information Processing Society
•EMEA Vice-Chair of Global IT Community Association
•Microsoft Certified Trainer (SharePoint, SQL Server, Security, Azure)
•Subject Matter Expert at CQURE
•SQL Server MVP (five years)
•MVP Mentor Program Member
•consultant, security & licensing auditor and trainer
•activeblogger, influencer, technicalwriter
•last9 yearslivingin Data Processing Center
•last 15 years banking and ICT
•NOW goingintoIndependent Consultancy
•frequentlyspeaker atseveralconferences: SQL Server Community Launch, Time for SharePoint, CodeCamps, InfoMEET, SharePoint Community Launch, CISSP Day, SQL in the City, InfoTRAMS, SQL Bits, IT Camp, SQL Saturday, CareerCon, Sharepoint& SQL Connection, Kariera IT, SQL Rally, SQL Relay, InfoTech…
•Microsoft TerminologyCommunity/ translationsfor Wndows7/8 and Visual Studio 2010/2012
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
3

4. AGENDA
•PART ONE: Slide Talks -introduction
plan, compability, features, functionality
•PART TWO: Demo Mode
sql server on premise & sql server in cloud
•PART THREE: Slide Talks –backup options
backup, plan, options
•PART FOUR: Show Time
backup, management
•APPENDIX
additional links, q&a
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
4

5. PART ONE: slide talks -introduction

6. SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
6
PART ONE: Private, IaaS, PaaS

7. PART ONE: AzureShortIntroduction
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
7
•Windows Azure
Compute:
Virtualized compute environment based
on Windows Server
Storage:
Durable, scalable, & available storage
Management:
Automated, model-driven management of the service
•SQL Azure (cloud-based database)
Database:
Relational processing for structured/unstructured data
•App Fabric (.NET services)
Service Bus:
General purpose application bus
Access Control:
Rules-driven, claims-based access control

8. Data Centersfor AzurePlatform
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
8

9. Data Centersfor AzurePlatform
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
9
North America
US Central -Iowa
US East -Virginia
US East 2 -Virginia
US GovIowa -Iowa
US GovVirginia -Virginia
US North Central -Illinois
US South Central -Texas
US West –California
Asia
Asia Pacific East -Hong Kong
Asia Pacific Southeast –Singapore
Europe
North Europe -Dublin, Ireland
West Europe -Amsterdam, Netherlands
Japan
Japan East -Saitama Prefecture
Japan West -Osaka Prefecture
Oceania (announced, coming soon)
Australia -Sydney, New South Wales
Australia -Melbourne, Victoria
SouthAmerica(preview)
Brasil-Sao Paulo,
Some datacenters have servers grouped inside containers -each containing
1800-2500 servers.

10. Security Requirementsfor AzurePlatform
AsaServiceProviderMicrosofthasanobligationtopassingtheseveralrulesforsecurity:
•ISO/IEC27001:2005
•SAS70Type1andII
Alsotheypassing(continuisly)severaldatasecuringaudits:
•PCIDSS
•SOXcompliance
•HIPAAcompliance
AndofcourserequirementsforDataCenters:
•Physical security of the data centers (locks, cameras, biometric devices, card readers, alarms)
•Firewalls, application gateways and IDS to protect the network
•Access Control Lists (ACLs) applied to virtual local area networks (VLANs) and applications
•Authentication and authorization of persons or processes that request access to data
•Hardening of the servers and operating system instances
•Redundant internal and external DNS infrastructure with restricted write access
•Securing of virtual machine objects
•Securing of static and dynamic storage containers
10
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

11. Security Requirementsfor AzurePlatform
•ISO/IEC 27001:2005 Audit and Certification
ISOScope:ThefollowingAzurefeaturesareinscopeforthecurrentISOaudit:CloudServices(includingFabricandRDFE),Storage(Tables, Blobs,Queues),VirtualMachines(includingwithSQLServer),VirtualNetwork,TrafficManager,WebSites,BizTalkServices,MediaServices, MobileServices,ServiceBus,Workflow,Multi-FactorAuthentication,ActiveDirectory,RightManagementService,SQLDatabase,andHDInsight. ThisincludestheInformationSecurityManagementSystem(ISMS)forAzure,encompassinginfrastructure,development,operations,andsupportforthesefeatures.AlsoincludedarePowerBIforOffice365andPowerQueryService.
•SOC 1 and SOC 2 SSAE 16/ISAE 3402 Attestations
Scope:ThefollowingAzurefeaturesareinscopeforthecurrentSOC1Type2andSOC2Type2attestations:CloudServices(includesstatelessWeb,andWorkerroles),Storage(Tables,Blobs,Queues),VirtualMachines(includespersistentvirtualmachinesforusewithsupportedoperatingsystems)andVirtualNetwork(includesTrafficManager).
•United Kingdom G-Cloud Impact Level 2 Accreditation
Scope:ThefollowingAzurefeaturesareinscopefortheIL2accreditation:VirtualMachines,CloudServices,Storage(Tables,Blobs,Queues, Drives),andVirtualNetwork.
•CloudSecurityAllianceCloudControlsMatrix
•FederalRiskandAuthorizationManagementProgram(FedRAMP)
•PaymentCardIndustry(PCI)DataSecurityStandards(DSS)Level1
•HIPAABusinessAssociateAgreement(BAA)
•FamilyEducationalRightsandPrivacyAct(FERPA)
11
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

12. Shared Environment
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
12
Hardware Boundary
Hardware Boundary
Hardware Boundary
Hardware Boundary
B
C
D
A
A
B
B
C
C
D
D
A

13. PART ONE: SQL Azurefewdaysago
We want to work with SQL Azure (oops SQL Database)
•Size doesmatter?
•Personal: 1GB, 5GB
•Business: 10GB, 20GB, 30GB, 40GB, 50GB, 100GB, 150GB (3x50)
•“Private”: less than 100 MB ($4.995 / month)
•Version doesmatter?
•10.25 my firstexperience, but afterJuly 2011 Service Release…
•11.0.9214.51 now > close to SQL Server 2012
•Row Versioning-Based Isolation Levels
•Both the READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION database options are set to ON in Microsoft Azure SQL Database.
•Because SET<snapshot_option>in the ALTER DATABASE Transact-SQL statement is not supported, these database options cannot be changed.
error msg 40544:
The database has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions.
13
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

14. PART ONE: SQL Azurenow
•Size doesmatter?
•Personal: 1GB, 5GB
•Business: 10GB, 20GB, 30GB, 40GB, 50GB, 100GB, 150GB (3x50)
•“Private”: less than 100 MB ($4.995 / month)
•Size doesmatter!
•BASIC
•size: 100MB, 500MB, 1GB, 2GB
•performance: 5DTU
•STANDARD
•size: 100MB, 500MB, 1GB, 2GB, 5GB, 10GB, 20GB, 30GB, 40GB, 50GB, 100GB, 150GB, 200GB, 250GB
•performance: S0 10DTU, S1 20DTU, S2 50DTU
•PREMIUM
•size: 100MB, 500MB, 1GB, 2GB, 5GB, 10GB, 20GB, 30GB, 40GB, 50GB, 100GB, 150GB, 200GB, 250GB, 500GB
•performance: P10 100DTU, P2 200DTU, SP3 800DTU
WhatisDTU
DTUs provide a way to describe the relative capacity of a performance level of Basic, Standard, and Premium databases. DTUs are based on a blended measure of CPU, memory, reads, and writes.
14
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

15. PART ONE: SQL Azureand DTU
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
15
Service Tier/Performance Level
DTU
MAX DB Size
MaxWorkerThreads
MaxSessions
Benchmark Transaction Rate
Predictability
Basic
5
2 GB
30
300
16,600 transactions per hour
Good
Standard/S0
10
250 GB
60
600
521 transactions
per minute
Better
Standard/S1
20
250 GB
90
900
934 transactions
per minute
Better
Standard/S2
50
250 GB
120
1,200
2,570 transactions per minute
Better
Premium/P1
100
500 GB
200
2,400
105 transactions
per second
Best
Premium/P2
200
500 GB
400
4,800
228 transactions per second
Best
Premium/P3
800
500 GB
1,600
19,200
735 transactions
per second
Best

16. PART ONE: SQL AzureCollation
•Collationdoes it matter?
•default database collation used by Microsoft Azure SQL Database is SQL_LATIN1_GENERAL_CP1_CI_AS, where LATIN1_GENERAL is English (United States), CP1 is code page 1252, CI is case-insensitive, and AS is accent-sensitive
SQL_Latin1_General_CP1_CI_AS
•When using an on-premiseSQL Server, you can set collations at server, database, column, and expression levels.
•Microsoft Azure SQL Database does not allow setting the collation at the server level.
•To use the non-default collation with Microsoft Azure SQL Database, set the collation with the Create Database Collate option, or at the column level or the expression level.
•SQL Database does not support the Collate option with the Alter Database command.
•By default, in SQL Database, temporary data will have the same collation as the database
16
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

17. SQLServer 2005 {9.0} NON-Compability
•Common Language Runtime (CLR) and CLR User-Defined Types
•Database Mirroring
•Service Broker
•Table Partitioning
•Typed XML and XML indexing is not supported. The XML data type is supported by SQL Azure.
17
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

18. SQL Server 2008 {10.0} NON-Compability
•Change Data Capture
•Data Auditing
•Data Compression
•Extended Events
•External Key Management / Extensible Key Management
•FILESTREAM Data
•Integrated Full-Text Search
•Large User-Defined Aggregates (UDAs)
•Large User-Defined Types (UDTs)
•Performance Data Collection (Data Collector)
•Policy-Based Management
•Resource Governor
•SQL Server Replication
•Transparent Data Encryption
18
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

19. SQL Server 2008R2 {10.50} NON-Compability
•SQL Server Utility
•SQL Server PowerShell Provider
•Master Data Services
SQL Server Management Studio
does not support Windows Azure SQL Database in versions prior to
SQL Server 2008 R2
19
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

20. PART ONE: Adventure with WASD
Adventure…
… of course Adventure Works 2012 for SQL Database
•Adventure Works for SQL Server 2012
•Release date: March 2012
•Adventure Works for SQL Azure
•Release date: April 2012
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
20

21. PART TWO: demo mode –first step

22. PART TWO: basic database
•sql azure database
•sql premise database
•portal
•management studio
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
22

23. PART THREE: slide talks –backup options

24. Backup Strategy
WhatisBackup?
WhatisStrategy?
Willwe needthis?
24
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

25. ITS ONLY ONE: BE PREPARED
Backups
•abouttypeof backup ( simplerm/ fullrm)
•aboutplace for storedbackup data
•aboutbackup window
•aboutprocedureusedfor backup
•aboutbackup tools
•aboutbackup of „backup logs”
•about estimated time for executing backup
•about REAL TIME of executing backup
BEST PRACTICE FOR SURVIVING DISASTER
25
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

26. In the request,backup,should include the followinginformation: • Informationabout theoperating systemandapplication versionforonline backupand installedupdates forthese components•a filebackuppolicy, in particular: anumber ofversionsof a filestoredthe storage timeofthe nextversion of the filethe frequency ofexecutionofsuchincrementalbackupswith the proposalof their implementation•OnlineBackupPolicythe storage timeofa fullbackupwithstorage timesuchan incrementalbackupthetimeof transactionlog filesthe frequency ofexecutionofa fullbackupwith the proposaldeadline for itsimplementationthe frequency ofexecutionofthe transactionlogbackup• Informationabout treesdirectories /filesthatshould be omittedorincludedduringbackuptasks(include /exclude list) •Number and type/ modelof physical processors, • Does thenodewill use theconnection to theSANtoimplementbackup
BACKUP > extractfrom SOP*
26
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

27. This registercontains information abouta backupplanimplemented.
•Backupfile space:
•numberofversions of a filestored in abackup
•numberof daysthat are keptmoreversions of a file
•numberofversionsof a filestored in thebackupsystemafter its removalfrom client device
•numberofdays thatwill storethe latest version ofthe deletedfilefrom the client device
•numberofdaysthatwill bestored inthe archive
•OnlineBackup:
•numberofbackupsstored infullbackup
•numberofincrementalbackups/diff/ fullstored in thebackup
•frequencyof transactionlogbackupsstored in thebackup (for databases)
•numberof days thebackupsto be storedon-linebackupsystem
•The listof nodesdefined in the systembackup:
•Domain|Node name|IP address ofthe node
•The list of definedbackuptasks(calledschedule)
•name of the task(schedule) |execution time
•a period of atwhichthe task isrepeated
BACKUP (registry) > extractfrom SOP*
27
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

28. RestoreStrategy
WhatisRestore?
WhatisStrategy?
Willwe needthis?
28
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

29. Best practicesby BrentOzar
SQL Server Backup Best Practices|
Written on October 17, 2007 by Brent Ozarin SQL Server
>> http://bit.ly/12oXm4h
I’ve been backing up SQL Servers for almost a decade now, and it’s time to share the lessons I’ve learned. All of this is my own opinion –your mileage may vary –but I’ll try to explain the reasoning behind the choices I make. I won’t address log shipping or snapshots this time around.
•Never back up databases to local disk.
•Back up databases to a fileshare, then back the share up to tape.
•Cost justify the network share with lower licensing costs & simpler backups.
•Back up to a different SAN if possible.
•My sweet spot for the backup array is raid 10 SATA.
•Backup agents like NetBackupand Backup Exec mean giving up scheduling control.
•Do regular fire drill rebuilds and restores.
•Build a standalone restore testbed.
•Keep management informed on restore time estimates.
•Trust no one.
29
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

30. ITS ONLY ONE: BE PREPARED
Restore
•abouttypeof backup ( simplerm/ fullrm)
•aboutplace for storedbackup data
•aboutthe proceduresof recovery
•aboutestimatedtimefor recovery
•aboutREAL TIME for recovery
•abouttoolsfor recovery
•aboutCorporateBackup Manager
•aboutpasswordfor accessto library
BEST PRACTICE FOR SURVIVING DISASTER
30
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

31. Register for Recovery/Restore/ReplacementTests
This registercontains information aboutthe testsand replacementof part or allof the environment.It consistsof the followingfields:
•the date of commencementand completionofthe recoverytest
•clientfor which thetestwas performedrecoverytest
•serversinvolvedin testingand replacement
•extent of testingand replacement
•person/ personsperforming therecoverytest
•person on theclientsideacceptsthe correctness ofthe recoverytest
•subsequentto the recoverytest
RESTORE > extractfrom SOP*
31
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

32. PART THREE: Azure SQL Database Backup and Restore
Microsoft Azure SQL Database has built-in backups to support self-service Point in Time Restore and Geo-Restore for Basic, Standard, and Premium service tiers.
If you have Web or Business Edition databases, you must create your own backup strategy. You can use database copy or Import and Export services to create copies of the data and export the file to an Microsoft Azure storage account.
Built-in Automatic Backup in Azure SQL Database>> Azure SQL Database automatically creates backups of every active database using the following schedule:
•fulldatabase backup once a week,
•differential database backups once a day,
•transaction log backups every 5 minutes.
The full and differential backups are replicated across regions to ensure availability of the backups in the event of a disaster.
32
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

33. PART THREE: Azure SQL Database Backup and Restore
BackupstorageisthestorageassociatedwithyourautomateddatabasebackupsthatareusedforPointinTimeRestoreandGeo-Restore.AzureSQLDatabaseprovidesupto200%ofyourmaximumprovisioneddatabasestorageofbackupstorageatnoadditionalcost.
Forexample,ifyouhaveadatabaseintheStandardservicetierwithaprovisionedsizeof250GB,youwillbeprovidedwith500GBofbackupstorageatnoadditionalcharge.
PointinTimeRestoreisdesignedtorecoveradatabasetoaspecificpointintimewithinthebackupretentionperiodsupportedbytheservicetierofthedatabase.Restoringcreatesanewdatabasewiththesameservicetierthatwasinuseatthechosenrestorepointandthelowestperformancelevelsupportedbythattier.
Forexample,ifyourestoreadatabasewhichwassettoPremiumatthespecifiedrestorepointintime,thenewdatabasewillalsobeaPremiumdatabaseandtheperformancelevelissettoP1
33
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

34. PART THREE: Azure SQL Database Backup and Restore
Service Tier
Geo-Restore
Self-Service Point in Time Restore
Backup Retention Period
Restore a Deleted Database
Web
Not supported
Not supported
n/a
n/a
Business
Not supported
Not supported
n/a
n/a
Basic
Supported
Supported
7 days
√
Standard
Supported
Supported
14 days
√
Premium
Supported
Supported
35 days
√
The timetaken to complete a restore depends on the size of the database and the length of the log chain. To get a good estimate of the restore time, you should periodically test restoring the database.
You can monitor the restore operation usingsys.dm_operation_status.
34
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

35. PART THREE: SQL Server Backup and Restore with Windows Azure Blob Storage Service
•SQLServerbackupstoandrestoringfromtheWindowsAzureBlobstorageservice.ItalsoprovidesasummaryofthebenefitsofusingtheWindowsAzureBlobservicetostoreSQLServerbackups.
•SQLServersupportsstoringbackupstotheWindowsAzureBlobstorageserviceinthefollowingways:
•ManageyourbackupstoWindowsAzure:UsingthesamemethodsusedtobackuptoDISKandTAPE,youcannowbackuptoWindowsAzurestoragebySpecifyingURLasthebackupdestination.Youcanusethisfeaturetomanuallybackuporconfigureyourownbackupstrategylikeyouwouldforalocalstorageorotheroff-siteoptions.ThisfeatureisalsoreferredtoasSQLServerBackuptoURL.Formoreinformation,seeSQLServerBackuptoURL.ThisfeatureisavailableinSQLServer2012SP1CU2orlater.
35
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

36. PART THREE: SQL Server Backup and Restore with Windows Azure Blob Storage Service
BenefitsofUsingtheWindowsAzureBlobServiceforSQLServerBackups
•Flexible,reliable,andlimitlessoff-sitestorage:
StoringyourbackupsonWindowsAzureBlobservicecanbeaconvenient,flexible,andeasytoaccessoff-siteoption. Creatingoff-sitestorageforyourSQLServerbackupscanbeaseasyasmodifyingyourexistingscripts/jobsBychoosingtogeoreplicatetheBlobstorageyouhaveanextralayerofprotectionintheeventofadisasterthatcouldaffectthewholeregion.Inaddition,backupsareavailablefromanywhereandatanytimeandcaneasilybeaccessedforrestores.
•BackupArchive:
TheWindowsAzureBlobStorageserviceoffersabetteralternativetotheoftenusedtapeoptiontoarchivebackups. Tapestoragemightrequirephysicaltransportationtoanoff-sitefacilityandmeasurestoprotectthemedia.StoringyourbackupsinWindowsAzureBlobStorageprovidesaninstant,highlyavailable,andadurablearchivingoption.
•Nooverheadofhardwaremanagement:
ThereisnooverheadofhardwaremanagementwithWindowsAzureservices.WindowsAzureservicesmanagethehardwareandprovidegeo-replicationforredundancyandprotectionagainsthardwarefailures.
•CostBenefits:
Payonlyfortheservicethatisused.Canbecost-effectiveasanoff-siteandbackuparchiveoption.SeetheWindowsAzureBillingConsiderationssectionformoreinformationandlinks.
36
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

37. PART THREE: SQL Server Backup and Restore with Windows Azure Blob Storage Service
BenefitsofUsingtheWindowsAzureBlobServiceforSQLServerBackups
•CurrentlyforinstancesofSQLServerrunninginaWindowsAzureVirtualMachine, backinguptoWindowsAzureBlobstorageservicescanbedonebycreatingattacheddisks.
However,thereisalimittothenumberofdisksyoucanattachtoaWindowsAzureVirtualMachine.Thislimitis16disksforanextralargeinstanceandfewerforsmallerinstances.ByenablingadirectbackuptoWindowsAzureBlobStorage,youcanbypassthe16disklimit.
•Inaddition,thebackupfilewhichnowisstoredintheWindowsAzureBlobstorageserviceisdirectlyavailabletoeitheranon-premisesSQLServeroranotherSQLServerrunninginaWindowsAzureVirtualMachine,withouttheneedfordatabaseattach/detachordownloadingandattachingtheVHD.
37
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud

38. PART FOUR: demo mode –next step

39. PART TWO: backup database
•backup
•restore
•automation
•backup to url
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
39

40. PART TWO: error
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
40
Error SQL71564:
The element Default: [dbo].[SystemDateDefault]
is not supported when used as part of a data package (.bacpac file)
Generate DROP statements for all extended propertiesby Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson/archive/2012/03/25/generate-drop-statements-for-all- extended-properties.aspx

41. Don’tAskMe…

42. SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
42

43. APPENDIX: links& demos

44. Important Article (in my private opinion)
http://bit.ly/WIHlDL
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
44
Authors:Conor Cunningham,Tobias Ternström,Silvano Coriani,Ewan Fairweather
Contributing Author:Ralph Squillace

45. MSDN SQL Database District
Windows Azure SQL Database (formerly SQL Azure)| http://bit.ly/H0Wdfx
•What's New in Windows Azure SQL Database (formerly SQL Azure)
•Backward Compatibility in Windows Azure SQL Database
•Known Issues in Windows Azure SQL Database
•Introducing Windows Azure SQL Database
•Tutorials
•Feedback and Community Information
•Windows Azure Platform Management Portal
•Windows Azure SQL Database Concepts
•Administration
•Development
•Guidelines and Limitations
•Management REST API Reference
•Transact-SQL Reference
•Errors and Exceptions Reference
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
45

46. APPENDIX: additionallinks
•Red Gate Cloud Ready Services
•http://cloudservices.red-gate.com/
•General Guidelines and Limitations (Windows Azure SQL Database)
•http://bit.ly/11wB6cK
•Adventure Works for SQL Database (formerly SQL Azure)
•http://bit.ly/125s0W0
•Federations: Building Scalable, Elastic, and Multi-tenant Database Solutions
•http://bit.ly/ZxzjmQ
•http://bit.ly/15GzIEE
•Error Messages (Windows Azure SQL Database)
•http://bit.ly/17tnQtE
•Compare SQL Server with Windows Azure SQL Database
•http://bit.ly/15RyB5u
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
46

47. Just Azure
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
47
http://JustAzure.com

48. AFTER SESSION
CONTACT:
•MAIL: KoprowskiT@windowslive.com
•MSG: KoprowskiT@windowslive.com
•TWITTER/FACEBOOK/LINKEDIN: KoprowskiT
SLIDES FROM SESSION:
•SQL Relay2014 Page: https://www.sqlsaturday.com/311/schedule.aspx
•SlideShareProfile: http://www.slideshare.net/Anorak
BLOGS:
•ITPRO Anorak’sVision: http://itblogs.pl/notbeautifulanymore/[PL/EN]
•Volume LicensingSpecialites: http://koprowskit.eu/licensing/[PL]
•My MVP Blog: http://koprowskit.eu/geek/[EN/ES/PL]
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
48

49. PLEASE REMEMBER:
Raffle at the End
in main ‚theatre’ auditorium
Feedback on site
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
49

50. Thank You Very Much
Q & A
SQL Relay 2014 | Birmingham Oct 29th | KoprowskiT - SQL Server in
the Cloud - from Plan to Backup to CLoud
50

51. Our awesome sponsors