KoprowskiT_SQLRelay2014#9_London_FromPlanToBackupToCloud

SQL Server in the CloudFrom Plan, To Backup, To Cloud

Tobiasz Janusz Koprowski | Independent Consultant

Our awesome sponsors

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

• active blogger, influencer, technical writer

• last 9 years living in Data Processing Center

• last 15 years banking and ICT

• NOW going into Independent Consultancy

• frequently speaker at several conferences: 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 Terminology Community / translations for Wndows 7/8 and Visual Studio 2010/2012

SQL Relay 2014 | London Oct 30th | KoprowskiT - SQL Server in the Cloud - from Plan to Backup to CLoud

3

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


4

PART ONE:slide talks - introduction


6

PART ONE: Private, IaaS, PaaS

PART ONE: Azure Short Introduction


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

Data Centers for Azure Platform


8

Data Centers for Azure Platform


9

North America

US Central - Iowa

US East - Virginia

US East 2 - Virginia

US Gov Iowa - Iowa

US Gov Virginia - 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

South America (preview)

Brasil - Sao Paulo,

Some datacenters have servers

grouped inside containers - each

containing 1800-2500

servers.

Security Requirements for Azure Platform

As a Service Provider Microsoft has an obligation to passing the several rules for security:

• ISO/IEC 27001:2005

• SAS 70 Type 1 and II

Also they passing (continuisly) several data securing audits:

• PCI DSS

• SOX compliance

• HIPAA compliance

And of course requirements for Data Centers:

• 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

10SQL Relay 2014 | London Oct 30th | KoprowskiT - SQL Server in the

Cloud - from Plan to Backup to CLoud

Security Requirements for Azure Platform

• ISO/IEC 27001:2005 Audit and CertificationISO Scope: The following Azure features are in scope for the current ISO audit: Cloud Services (including Fabric and RDFE), Storage (Tables,

Blobs, Queues), Virtual Machines (including with SQL Server), Virtual Network, Traffic Manager, Web Sites, BizTalk Services, Media Services,

Mobile Services, Service Bus, Workflow, Multi-Factor Authentication, Active Directory, Right Management Service, SQL Database, and HDInsight.

This includes the Information Security Management System (ISMS) for Azure, encompassing infrastructure, development, operations, and

support for these features. Also included are Power BI for Office 365 and Power Query Service.

• SOC 1 and SOC 2 SSAE 16/ISAE 3402 AttestationsScope: The following Azure features are in scope for the current SOC 1 Type 2 and SOC 2 Type 2 attestations: Cloud Services (includes stateless

Web, and Worker roles), Storage (Tables, Blobs, Queues), Virtual Machines (includes persistent virtual machines for use with supported

operating systems) and Virtual Network (includes Traffic Manager).

• United Kingdom G-Cloud Impact Level 2 AccreditationScope: The following Azure features are in scope for the IL2 accreditation: Virtual Machines, Cloud Services, Storage (Tables, Blobs, Queues,

Drives), and Virtual Network.

• Cloud Security Alliance Cloud Controls Matrix

• Federal Risk and Authorization Management Program (FedRAMP)

• Payment Card Industry (PCI) Data Security Standards (DSS) Level 1

• HIPAA Business Associate Agreement (BAA)

• Family Educational Rights and Privacy Act (FERPA)



Shared Environment


12

Hardware Boundary

Hardware Boundary

Hardware Boundary

Hardware Boundary

BC

D

A A

B

B

C

CD

D

A

PART ONE: SQL Azure few days ago We want to work with SQL Azure (oops SQL Database)

• Size does matter?

• Personal: 1GB, 5GB

• Business: 10GB, 20 GB, 30 GB, 40 GB, 50 GB, 100 GB, 150 GB (3x50)

• “Private”: less than 100 MB ($4.995 / month)

• Version does matter?

• 10.25 my first experience, but after July 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.



http://blogs.msdn.com/b/windowsazure/archive/2011/07/13/announcing-sql-azure-july-2011-service-release.aspx

PART ONE: SQL Azure now• Size does matter?

• Personal: 1GB, 5GB

• Business: 10GB, 20 GB, 30 GB, 40 GB, 50 GB, 100 GB, 150 GB (3x50)

• “Private”: less than 100 MB ($4.995 / month)

• Size does matter!

• 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

What is DTUDTUs 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.



PART ONE: SQL Azure and DTU


15

Service Tier/Performance Level

DTU MAX DB Size Max Worker Threads Max SessionsBenchmark Transaction

RatePredictability

Basic

5 2 GB 30 30016,600 transactions

per hourGood

Standard/S0

10 250 GB 60 600521 transactions

per minuteBetter

Standard/S1

20 250 GB 90 900934 transactions

per minuteBetter

Standard/S2

50 250 GB 120 1,2002,570 transactions per

minuteBetter

Premium/P1

100 500 GB 200 2,400105 transactions

per secondBest

Premium/P2

200 500 GB 400 4,800228 transactions per

secondBest

Premium/P3

800 500 GB 1,600 19,200735 transactions

per secondBest

PART ONE: SQL Azure Collation• Collation does 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-premise SQL 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



SQL Server 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.



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



SQL Server 2008R2 {10.50} NON-Compability

• SQL Server Utility

• SQL Server PowerShell Provider

• Master Data Services

SQL Server Management Studiodoes not support Windows Azure SQL Database in versions prior to

SQL Server 2008 R2



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


20

PART TWO: demo mode – first step

PART TWO: basic database


22

PART TWO: basic database

• sql azure database

• sql premise database

• portal

• management studio


23

PART THREE:slide talks – backup options

Backup Strategy

What is Backup?

What is Strategy?

Will we need this?



ITS ONLY ONE: BE PREPARED

Backups

• about type of backup ( simple rm / full rm)

• about place for stored backup data

• about backup window

• about procedure used for backup

• about backup tools

• about backup of „backup logs”

• about estimated time for executing backup

• about REAL TIME of executing backup

BEST PRACTICE FOR SURVIVING DISASTER



In the request, backup, should include the following information:• Information about the operating system and application version for online backup and installed updates for these components• a file backup policy, in particular:

a number of versions of a file storedthe storage time of the next version of the filethe frequency of execution of such incremental backups with the proposal of their

implementation• Online Backup Policy

the storage time of a full backup with storage time such an incremental backupthe time of transaction log filesthe frequency of execution of a full backup with the proposal deadline for

its implementationthe frequency of execution of the transaction log backup

• Information about trees directories / files that should be omittedor included during backup tasks (include / exclude list)• Number and type / model of physical processors,• Does the node will use the connection to the SAN to implement backup

BACKUP > extract from SOP*



This register contains information about a backup plan implemented.

• Backup file space:

• number of versions of a file stored in a backup

• number of days that are kept more versions of a file

• number of versions of a file stored in the backup system after its removal from client device

• number of days that will store the latest version of the deleted file from the client device

• number of days that will be stored in the archive

• Online Backup:

• number of backups stored in full backup

• number of incremental backups / diff / full stored in the backup

• frequency of transaction log backups stored in the backup (for databases)

• number of days the backups to be stored on-line backup system

• The list of nodes defined in the system backup:

• Domain | Node name | IP address of the node

• The list of defined backup tasks (called schedule)

• name of the task (schedule) | execution time

• a period of at which the task is repeated

BACKUP (registry) > extract from SOP*



Restore Strategy

What is Restore?

What is Strategy?

Will we need this?



Best practices by Brent Ozar

SQL Server Backup Best Practices |

Written on October 17, 2007 by Brent Ozar in 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 NetBackup and 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.



http://bit.ly/12oXm4h

ITS ONLY ONE: BE PREPARED

Restore

• about type of backup ( simple rm / full rm)

• about place for stored backup data

• about the procedures of recovery

• about estimated time for recovery

• about REAL TIME for recovery

• about tools for recovery

• about Corporate Backup Manager

• about password for access to library

BEST PRACTICE FOR SURVIVING DISASTER



Register for Recovery/Restore/Replacement Tests

This register contains information about the tests and replacement of part or all of the environment. It consists of the following fields:

• the date of commencement and completion of the recovery test

• client for which the test was performed recovery test

• servers involved in testing and replacement

• extent of testing and replacement

• person / persons performing the recovery test

• person on the client side accepts the correctness of the recovery test

• subsequent to the recovery test

RESTORE > extract from SOP*



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:

• full database 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.




Backup storage is the storage associated with your automated database backups that are used for Point in TimeRestore and Geo-Restore. Azure SQL Database provides up to 200% of your maximum provisioned databasestorage of backup storage at no additional cost.

For example, if you have a database in the Standard service tier with a provisioned size of 250 GB, you will beprovided with 500 GB of backup storage at no additional charge.

Point in Time Restore is designed to recover a database to a specific point in time within the backup retention periodsupported by the service tier of the database. Restoring creates a new database with the same service tier that was inuse at the chosen restore point and the lowest performance level supported by that tier.

For example, if you restore a database which was set to Premium at the specified restore point in time, the newdatabase will also be a Premium database and the performance level is set to P1




Service Tier Geo-RestoreSelf-Service Point in

Time RestoreBackup Retention

PeriodRestore 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 time taken 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 using sys.dm_operation_status.



http://go.microsoft.com/fwlink/?LinkID=397450

PART THREE: SQL Server Backup and Restore with Windows Azure Blob Storage Service• SQL Server backups to and restoring from the Windows Azure Blob storage service. It also provides a summary of

the benefits of using the Windows Azure Blob service to store SQL Server backups.

• SQL Server supports storing backups to the Windows Azure Blob storage service in the following ways:

• Manage your backups to Windows Azure: Using the same methods used to backup to DISK and TAPE, you cannow back up to Windows Azure storage by Specifying URL as the backup destination. You can use this feature tomanually backup or configure your own backup strategy like you would for a local storage or other off-siteoptions. This feature is also referred to as SQL Server Backup to URL. For more information, see SQL ServerBackup to URL. This feature is available in SQL Server 2012 SP1 CU2 or later.



http://www.windowsazure.com/en-us/develop/net/how-to-guides/blob-storage/

http://msdn.microsoft.com/en-us/library/dn435916.aspx

PART THREE: SQL Server Backup and Restore with Windows Azure Blob Storage ServiceBenefits of Using the Windows Azure Blob Service for SQL Server Backups

• Flexible, reliable, and limitless off-site storage:

Storing your backups on Windows Azure Blob service can be a convenient, flexible, and easy to access off-site option.Creating off-site storage for your SQL Server backups can be as easy as modifying your existing scripts/jobsBy choosingto geo replicate the Blob storage you have an extra layer of protection in the event of a disaster that could affect thewhole region. In addition, backups are available from anywhere and at any time and can easily be accessed for restores.

• Backup Archive:

The Windows Azure Blob Storage service offers a better alternative to the often used tape option to archive backups.Tape storage might require physical transportation to an off-site facility and measures to protect the media. Storingyour backups in Windows Azure Blob Storage provides an instant, highly available, and a durable archiving option.

• No overhead of hardware management:

There is no overhead of hardware management with Windows Azure services. Windows Azure services manage thehardware and provide geo-replication for redundancy and protection against hardware failures.

• Cost Benefits:

Pay only for the service that is used. Can be cost-effective as an off-site and backup archive option. See the WindowsAzure Billing Considerations section for more information and links.



http://msdn.microsoft.com/en-us/library/jj919148.aspx#Billing

PART THREE: SQL Server Backup and Restore with Windows Azure Blob Storage Service

Benefits of Using the Windows Azure Blob Service for SQL Server Backups

• Currently for instances of SQL Server running in a Windows Azure Virtual Machine,backing up to Windows Azure Blob storage services can be done by creating attacheddisks.

However, there is a limit to the number of disks you can attach to a Windows Azure Virtual Machine. This limit is 16disks for an extra large instance and fewer for smaller instances. By enabling a direct backup to Windows Azure BlobStorage, you can bypass the 16 disk limit.

• In addition, the backup file which now is stored in the Windows Azure Blob storageservice is directly available to either an on-premises SQL Server or another SQL Serverrunning in a Windows Azure Virtual Machine, without the need for database attach/detachor downloading and attaching the VHD.



PART FOUR:demo mode – next step

PART TWO: backup database

• backup

• restore

• automation

• backup to url


40

PART TWO: error


41

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 properties by Jamie Thomson

http://sqlblog.com/blogs/jamie_thomson/archive/2012/03/25/generate-drop-statements-for-all-extended-properties.aspx

http://sqlblog.com/blogs/jamie_thomson/archive/2012/03/25/generate-drop-statements-for-all-extended-properties.aspx

Don’tAsk Me…


43

APPENDIX: links & demos

Important Article (in my private opinion)

http://bit.ly/WIHlDL


45

Authors: Conor Cunningham, Tobias Ternström, Silvano Coriani, Ewan Fairweather

Contributing Author: Ralph Squillace

MSDN SQL Database DistrictWindows 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


46

http://bit.ly/H0Wdfx

Just Azure


47

http://JustAzure.com

http://justazure.com/

APPENDIX: additional links• 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


48

http://cloudservices.red-gate.com/

http://bit.ly/11wB6cK

http://bit.ly/125s0W0

http://bit.ly/ZxzjmQ

http://bit.ly/15GzIEE

http://bit.ly/17tnQtE

http://bit.ly/15RyB5u

MSDN SQL Database DistrictWindows 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


49

http://bit.ly/H0Wdfx

• Red Gate Cloud Ready Services

• http://cloudservices.red-gate.com/

• Windows Azure DataCenter Video

http://www.youtube.com/watch?v=JJ44hEr5DFE

• 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

APPENDIX: additional links


50

http://cloudservices.red-gate.com/

http://www.youtube.com/watch?v=JJ44hEr5DFE

http://bit.ly/11wB6cK

http://bit.ly/125s0W0

http://bit.ly/ZxzjmQ

http://bit.ly/15GzIEE

http://bit.ly/17tnQtE

http://bit.ly/15RyB5u

• Trust Center: Security, Privacy and Compliance Information for Office 365 and Microsoft Dynamics CRM Online

• http://bit.ly/1q4i8bY

• Announcing PCI DSS compliance and expanded ISO certification for Windows Azure

• http://bit.ly/1tyt7vE

• Windows Azure cloud services achieve critical federal security milestone

• http://bit.ly/1osDHfi

• INFOSYS – Microsoft Data Access Technologies SWOT

• http://infy.com/1kgujKC

• One year in, and the use cases for Microsoft's SQL Azure are becoming clear

• http://bit.ly/TYWRRV



51

http://bit.ly/1q4i8bY

http://bit.ly/1tyt7vE

http://bit.ly/1osDHfi

http://infy.com/1kgujKC

http://bit.ly/TYWRRV

• New Levels of Security via Machine Learning & Combined Data Sets

• http://bit.ly/1s6seth

• Predict What's Next: Getting Started on Azure Machine Learning - Part 1

• http://bit.ly/1BLfWq1

• Predict What's Next: How to Get Started with Machine Learning Part 2

• http://bit.ly/1BLg099

• Introducing Elastic Scale preview for Azure SQL Database

• http://bit.ly/1xZk5sG

• New D-Series Virtual Machine Sizes

• http://bit.ly/10IapFg



52

http://bit.ly/1s6seth

http://bit.ly/1BLfWq1

http://bit.ly/1BLg099

http://bit.ly/1xZk5sG

http://bit.ly/10IapFg

APPENDIX: additional links• Windows Azure IT Camp Resources–Slide Deck and Hands-on-Lab

• http://blogs.technet.com/b/bobh/archive/2013/09/18/windows-azure-it-camp-resources-slide-deck-and-hands-on-lab.aspx#sthash.yFgxwPLv.dpuf

• Microsoft Azure Free one month trial

• http://azure.microsoft.com/en-us/pricing/free-trial/?WT.mc_id=AB7B32386

• Microsoft Virtual Academy

• http://azure.microsoft.com/en-us/pricing/free-trial/?WT.mc_id=AB7B32386

• Introducing Elastic Scale preview for Azure SQL Database

• http://azure.microsoft.com/blog/2014/10/02/introducing-elastic-scale-preview-for-azure-sql-database/

• Performance Best Practices for SQL Server in Azure Virtual Machines

• http://msdn.microsoft.com/en-us/library/azure/dn133149.aspx?WT.mc_id=Social_SQL_General_DI&WT.mc_id=Social_FB_OutgoingPromotion_20140922_90669619_Microsoft%20SQL%20Server%20-%20sqlserver&linkId=9703972


53

http://blogs.technet.com/b/bobh/archive/2013/09/18/windows-azure-it-camp-resources-slide-deck-and-hands-on-lab.aspx#sthash.yFgxwPLv.dpuf

http://azure.microsoft.com/en-us/pricing/free-trial/?WT.mc_id=AB7B32386

http://azure.microsoft.com/en-us/pricing/free-trial/?WT.mc_id=AB7B32386

http://azure.microsoft.com/blog/2014/10/02/introducing-elastic-scale-preview-for-azure-sql-database/

http://msdn.microsoft.com/en-us/library/azure/dn133149.aspx?WT.mc_id=Social_SQL_General_DI&WT.mc_id=Social_FB_OutgoingPromotion_20140922_90669619_Microsoft SQL Server - sqlserver&linkId=9703972

APPENDIX: additional linksSQL Database Migration Wizard v3.11 & v4.11 & v5.11

• Project DescriptionSQL Database Migration Wizard (SQLAzureMW) is designed to help you migrate your SQL Server 2005/2008/2012/2014 databases to Azure SQL Database.

RequirementsSQLAzureMW v3x and tools requires .NET Framework 3.5 and SQL Server 2008 R2 SP1SQLAzureMW v4x and tools requires .NET Framework 4.5 and SQL Server 2012SQLAzureMW v5x and tools requires .NET Framework 4.5 and SQL Server 2014

• AzureMWBatchBackup:

• This is used to create a backup of a database schema and data. The data is downloaded via BCP. The TSQL output from SQLAzureMWBatchBackup can be used by SQLAzureMW or SQLAzureMWBatchUpload.

• SQLAzureMWBatchUpload:

• Takes the output from SQLAzureMW or SQLAzureMWBatchBackup and runs it against the target Azure SQLDatabase (or SQL Server) server.


54

http://sqlazuremw.codeplex.com/


55

CONTACT:

• MAIL: [email protected]

• MSG: [email protected]

• TWITTER/FACEBOOK/LINKEDIN: KoprowskiT

SLIDES FROM SESSION:

• SQL Relay 2014 Page: https://www.sqlsaturday.com/311/schedule.aspx

• SlideShare Profile: http://www.slideshare.net/Anorak

BLOGS:

• ITPRO Anorak’s Vision: http://itblogs.pl/notbeautifulanymore/ [PL/EN]

• Volume Licensing Specialites: http://koprowskit.eu/licensing/ [PL]

• My MVP Blog: http://koprowskit.eu/geek/ [EN/ES/PL]

AFTER SESSION



mailto:[email protected]

https://www.sqlsaturday.com/311/schedule.aspx

http://www.slideshare.net/Anorak

http://itblogs.pl/notbeautifulanymore/

http://koprowskit.eu/licensing/

http://koprowskit.eu/geek/

PLEASE REMEMBER:

Feedback on site


57

Thank You Very Much

Q & A


58

Our awesome sponsors

KoprowskiT_SQLRelay2014#9_London_FromPlanToBackupToCloud

Technology

Transcript of KoprowskiT_SQLRelay2014#9_London_FromPlanToBackupToCloud