SQL Track: Hybrid cloud with sql server 2014
Download as PPTX, PDF0 likes498 views
The document discusses the process of backing up and restoring SQL Server databases to Windows Azure, including the migration of existing databases and the necessary components like Azure storage accounts. It outlines the limitations and requirements for using Azure for SQL Server, such as size restrictions and the lack of GUI support, while detailing how to set up backups through T-SQL commands. Additionally, it highlights features like managed backups, point-in-time restore capabilities, and considerations for using Azure VM for SQL Server deployments.
![SQL Server Components
• URL
– http[s]://ACCOUNTNAME.Blob.core.windows.net/<CONTAINER>/<FILENAME.bak>
• Credential](https://image.slidesharecdn.com/hybridcloudwithsqlserver2014-140617150554-phpapp01/85/SQL-Track-Hybrid-cloud-with-sql-server-2014-6-320.jpg)
![What do you need?
• Policy on a container
• Shared access signature (SAS)
• SQL Server Credential
CREATE CREDENTIAL
[https://koherastorage.blob.core.windows.net/sqldatabasestorage]
WITH IDENTITY='SHARED ACCESS SIGNATURE',
SECRET = 'sr=c&si=sqlpolicy&sig=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'](https://image.slidesharecdn.com/hybridcloudwithsqlserver2014-140617150554-phpapp01/85/SQL-Track-Hybrid-cloud-with-sql-server-2014-18-320.jpg)
SQL Track: Hybrid cloud with sql server 2014
- 1. Hybrid Cloud with SQL Server 2014 Pieter Vanhove
- 3. Agenda Backup and Restore Databases SQL Server Data Files Migrate existing SQL Server databases
- 4. SQL Server backup to Windows Azure Cost - Effective Secure Durable Smart Consistent
- 5. Azure Account Container Blob Storage Account Adventureworks.bak MyDatabase.bak SQL Backup Files Windows Azure Components
- 6. SQL Server Components • URL – http[s]://ACCOUNTNAME.Blob.core.windows.net/<CONTAINER>/<FILENAME.bak> • Credential
- 7. T-SQL or UI BACKUP DATABASE AdventureWorks2012 TO URL = 'https://mystorageaccount.blob.core.windows.net/mycontainer/AdventureWorks2012.bak' WITH CREDENTIAL = 'mycredential' ,COMPRESSION ,STATS = 5; GO
- 8. DEMO
- 9. SQL Server Backup to Windows Azure Tool Rules Backup files Redirect Azure Storage
- 10. DEMO
- 11. Managed Backup to Windows Azure Automates SQL Server backups Retention period Workload on the database Supports point in time restore
- 12. When is a full backup scheduled Enabled the first time Data growth > 1 GB One week has passed The log chain is broken
- 13. When is a transaction log backup scheduled No backup history Log space > 5 MB 2 hours have passed Lagging behind
- 14. Limitations Only full and log backups No GUI, only T- SQL System Databases are not supported Only blob storage Maximum size of 1 TB Simple recovery model is not supported
- 15. DEMO
- 16. Agenda Backup and Restore Databases SQL Server Data Files Migrate existing SQL Server databases
- 17. Data Files in Windows Azure Windows Azure VM On-premise box Windows Azure Storage DB3 DB6DB6DB5DB4 DB3DB2DB1 Near “bottomless” storage Off-site, geo- redundant Fast Migration Best suited for read workloads
- 18. What do you need? • Policy on a container • Shared access signature (SAS) • SQL Server Credential CREATE CREDENTIAL [https://koherastorage.blob.core.windows.net/sqldatabasestorage] WITH IDENTITY='SHARED ACCESS SIGNATURE', SECRET = 'sr=c&si=sqlpolicy&sig=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
- 19. Create Database -- Create database with data and log files in Windows Azure container. CREATE DATABASE testdb ON ( NAME = testdb_dat, FILENAME = 'https://koherastorage.blob.core.windows.net/sqldatabasestorage/TestData.mdf' ) LOG ON ( NAME = testdb_log, FILENAME = 'https://koherastorage.blob.core.windows.net/sqldatabasestorage/TestLog.ldf')
- 20. Limitations No Filestream 1 instance can access the files No geo- replication No In- memory OLTP Maximum size of 1 TB No Failover Clustering
- 21. DEMO
- 22. Agenda Backup and Restore Databases SQL Server Data Files Migrate existing SQL Server databases
- 23. SQL Server VM Windows Azure Storage Deploy Database to a Windows Azure VM On premise SQL Servers
- 24. Benefits No Windows Azure knowledge required Multiple retry/recovery points Not overwriting or updating existing data Scalable for up to 1TB databases Connection is the biggest performance limiting
- 25. DEMO
- 26. Agenda Backup and Restore Databases SQL Server Data Files Migrate existing SQL Server databases
- 27. Q & A
- 28. AlwaysOn Integration with Windows Azure
- 31. Follow Technet Belgium @technetbelux Subscribe to the TechNet newsletter aka.ms/benews Be the first to know
- 32. Belgium’s biggest IT PRO Conference
Editor's Notes
- #19: How to configure? You must create a policy on a container and also generate a shared access signature (SAS) key. A shared access signature provides delegated access to resources in your storage account. This means that you can grant a client limited permissions to your blobs, queues, or tables for a specified period of time and with a specified set of permissions, without having to share your account access keys. The SAS is a URI that encompasses in its query parameters all of the information necessary for authenticated access to a storage resource. To access storage resources with the SAS, the client only needs to pass in the SAS to the appropriate constructor or method. For each container used by a data or a log file, you must create a SQL Server Credential whose name matches the container path. You must store the information regarding Windows Azure Storage container, its associated policy name, and SAS key in the SQL Server credential store.