SQL Database Service Import Export
•
0 j'aime•1,050 vues
A'dan Z'ye Windows Azure ile Uygulama Süreçleri http://www.ibrahimatay.com/post/2013/03/windows-azure-platform-ile-uygulama-yayinlama-surecleri-internet-semineri-notlari/ Windows Azure Platform ile Uygulama Yayınlama Süreçleri Internet Semineri Notları http://www.ibrahimatay.com/category/a-dan-z-ye-windows-azure-ile-uygulama-surecleri/
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Plus de İbrahim ATAY
Plus de İbrahim ATAY (20)
Dernier
Dernier (20)
SQL Database Service Import Export
- 1. İbrahim ATAY | Consultant www.ibrahimatay.org | @ibrahim_atay
- 3. SQL Database Service Import / Export Blob Storage BACPAC Copy BACPAC Upload/ Download Client-side Import/Export
- 10. Imaging VMs in the Cloud Cloud Base.VHD Identical/similar deployment instances using common OS image as start Capture VM Saves Customized Image to Your Image Library
- 12. İbrahim ATAY Software Consultant http://ibrahimatay.org @ibrahim_atay Ibrahim.atay@bilgeadam.com
- 13. Thank You
Notes de l'éditeur
- Slide Objectives:Outline the AgendaTransition:The topics discussed in the presentation focus on two main tools.Speaking Points:DAC Framework and then Import/Export ServiceSQL Server Data ToolsOther ToolsBest PracticesNotes:Any notes go here
- Slide Objectives:Understand the underlying architecture used for the Import / Export service and BACPACTransition:The architecture utilizes many of the Windows Azure features and represents the utilization of both on-premises services as well as Windows Azure services. Both on-premises and cloud services utilize the new BACPAC format in which both schema and data are encapsulated into the artifact. Speaking Points:Client-side Import/Export via DAC Framework and client-side libraries via SQL Server 2012 or Azure Import Export Service ClientHosted Windows Azure DAC Framework Import/Export service utilized by the Windows Azure Management PortalBACPAC artifact containing both Schema AND DataNotes:Any notes go here
- Slide Objectives:Highlight the requirements for using the Import/Export service and the DAC FrameworkTransition:There are specific requirements depending on if you are using only using the Import/Export service, or if you plan on using any of the client libraries. Speaking Points:You can either install SSMS and get all the components for free –or- install the specific dependencies and call the APIs directly and/or use the reference CLI which is here: http://sqldacexamples.codeplex.com/releases/view/807052012 – All necessary component installed2008 R2 to 2000 – DACFx, T-SQL Language Service, ScriptDOM, SMO, System CLR Types, DAC ImportExport Service Client Executable (1.6)To use the service you need to have a Windows Azure storage account and SQL Database server setup already. You only need to use the EXE or the wizard in the Windows Azure Management portal to perform the import/export. You don’t need all the dependencies if you plan on only using the serviceNotes:Any notes go here
- Slide Objectives:Explain how developers have a choice in publishing methods to Windows Azure Web Sites and that regardless of which method they choose publishing is fast and easy. You can even publish from a non-Windows machine using FTP or Git.Notes:
- Transition:Let’s spend a few minutes talking about what happens when we deploy a cloud service in Windows Azure.
- Slide ObjectiveCODE – PACKAGE – UPLOAD – DEPLOYShows how service makes it from code living in Visual Studio to a running deployed instance in Windows AzureShow how Roles are packaged up and uploaded with the config to Windows AzureSpeaking PointsCode is compiled, then packaged into a single file. This is the service package.This, along with the configuration/service model – are deployed via the web portal.NotesVisual Studio 2010 with the updated tools now supports automated seamless package/upload/deploy using Service Mngt Api
- Slide Objective:Explain how to create an image in the cloudNotes:This use case is about using the capture feature of IaaS to create OS images. The first part you start with a base vhd that you then custom with software binaries, registry settings etc.. You run sysprep.exe and generalize/shutdown the OS. You can then upload it if coming from on-premises or just click the capture button if you created the VM in the cloud. Capture allows you to take a generalized VM and save the underlying VHD as a new image in your image library.