You have two SQL Server instances named SQLDev and SQLProd that have access to
various storage media.
You plan to synchronize SQLDev and SQLProd.
You need to recommend a solution that meets the following requirements:
• The database schemas must be synchronized from SQLDev to SQLProd.
• The database on SQLDev must be deployed to SQLProd by using a package.
• The package must support being deployed to Windows Azure SQL Database.
What should you recommend?More than one answer choice may achieve the goal. Select
the BEST answer.
A.
A database snapshot
B.
SQL Server Integration Services (SSIS)
C.
Change data capture
D.
A data-tier application
Explanation:
* SIS supports connections to SQL Database by using the ADO.NET provider. OLEDB is not
supported at this time. You can build the SSIS package connecting to SQL Database and
create the data flow tasks the same way as you would against a typical on-premise SQL
Server.
D?
0
0
It probably would be D, because azure does not support SSIS
0
0
Yes azure not support SSIS. correct is D
0
0
https://msdn.microsoft.com/en-us/library/jj901708.aspx
Summary: SQL Server Integration Services (SSIS) can be used effectively as a tool for moving data to and from Windows Azure SQL Database.
0
0
RB – It is: Hybrid Data Movement
Correct answer is still D
0
0
https://msdn.microsoft.com/en-us/library/jj901708.aspx
0
0
I think B. SSIS is correct because : SQL Server Integration Services (SSIS) can be used effectively as a tool for moving data to and from Windows Azure SQL Database, as part of the total extract, transform, and load (ETL) solution and as part of the data movement solution. SSIS can be used effectively to move data between sources and destinations in the cloud, and in a hybrid scenario between the cloud and on-premise. This paper outlines best practices for using SSIS for cloud sources and destinations and for project planning for SSIS projects to be used with Azure or hybrid data moves, and gives an example of maximizing performance on a hybrid move by scaling out the data movement.
0
0
My answer is also B. SSIS
Migrating SQL Server to SQL Azure.
Watch this video tutorial
https://www.youtube.com/watch?v=ZZ5lFiJtbBU
0
0
‘The package must support being deployed to Windows Azure SQL Database.’
SSIS is able to adress SQL Azure as a source or destination; but you must DEPLOY the package to the Azure SQL Database; in my oppinion, there is a whole instance on a “regular” windows azure machine in the cloud”. There, the SSIS option exists.
So, answer B. is correct i think
0
0
for those who are for B(SSIS), what is wrong with D (DAC)?
0
0
More than one answer choice may achieve the goal. Select the BEST answer.
While one could use Data-Tier Application in SSMS to achieve the above, it requires more configuration and customization steps than using SSIS.
Option B (SSIS) provides in-built capabilities for achieving the above-scenario by using readily-available data-flow and control flow components of the DTS tools in SSIS, and is very compatible with Azure.
0
0
I think the answer is “D”.
“The database on SQLDev must be deployed to SQLProd by using a package” sounds like copy SQLDev schema into a DAC then deploy the DAC into On-premise SQL or Azure SQL Database.
https://www.visualstudio.com/en-us/docs/release/examples/azure/azure-web-apps-and-sql-db
0
0
The correct answer imho is D. Right click on the DB in SSMS, Select Tasks, Select Extract Data-tier application…
https://azure.microsoft.com/en-us/documentation/articles/sql-database-cloud-migrate/
0
0