You are developing a SQL Server Integration Services (SSIS) project to read and write data
from a Windows Azure SQL Database database to a server that runs SQL Server 2012.
The connection will be used by data flow tasks in multiple SSIS packages. The address of
the target Windows Azure SQL Database database will be provided by a project parameter.
You need to create a solution to meet the requirements by using the least amount of
administrative effort.
What should you do?
A.
Add a SQLMOBILE connection manager to each package.
B.
Add an ADO.NET project connection manager.
C.
Add a SQLMOBILE project connection manager.
D.
Add an ADO.NET connection manager to each data flow task.
E.
Add a SQLMOBILE connection manager to each data flow task.
F.
Add an ADO.NET connection manager to each package.
For sure. Could somebody present some logics in the background?
B
Question syas Azure SQL Database database….I think it is Azure SQL Compact database. That’s why answer is referring to SQLMOBILE connection manager.
I think it should be ADO.net (B)
the below link use ADO.net to load data into Azure :
https://www.simple-talk.com/cloud/cloud-data/uploading-data-to-windows-azure-sql-database/
B.
Add an ADO.NET project connection manager.
It’s B.
SQLMOBILE – Connects to a SQL Server Compact database not Azure SQL Database
https://msdn.microsoft.com/en-us/library/ms140203.aspx
B
B:
you can connect over ADO.Net:
https://www.mssqltips.com/sqlservertip/1937/read-and-write-data-from-sql-azure-using-sql-server-integration-services-2008-r2/
I think it is “A” based on the following info:
1. An ADO connection manager enables a package to connect to ActiveX Data Objects (ADO) objects, such as a recordset, from https://docs.microsoft.com/en-us/sql/integration-services/connection-manager/ado-connection-manager
2. When you add a SQL Server Compact connection manager to a package, Integration Services creates a connection manager that will resolve to a SQL Server Compact connection at run time and The ConnectionManagerType property of the connection manager is set to SQLMOBILE. From https://docs.microsoft.com/en-us/sql/integration-services/connection-manager/sql-server-compact-edition-connection-manager