Skip to content

Commit 44c6f9a

Browse files
PRMerger13PRMerger13
authored
Merge pull request #16133 from JKirsch1/revisedaddingalttext1
1750982 | Adding missing alt-text | 1 revised
2 parents 8fecd53 + 139edcf commit 44c6f9a

2 files changed

Lines changed: 32 additions & 32 deletions

File tree

‎docs/integration-services/load-data-to-sql-data-warehouse.md‎

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Visual Studio opens and creates a new Integration Services (SSIS) project. Then
6262
* In the middle, the design surface, with multiple tabs. You typically use at least the **Control Flow** and the **Data Flow** tabs.
6363
* On the right, the **Solution Explorer** and the **Properties** panes.
6464

65-
![][01]
65+
![Screenshot of Visual Studio showing the Toolbox pane, the design pane, the Solution Explorer pane, and the Properties pane.][01]
6666

6767
## Option 1 - Use the SQL DW Upload task
6868

@@ -115,23 +115,23 @@ To continue the tutorial with this option, you need the following things:
115115
### Create the basic data flow
116116
1. Drag a Data Flow Task from the Toolbox to the center of the design surface (on the **Control Flow** tab).
117117

118-
![][02]
118+
![Screenshot of Visual Studio showing a Data Flow Task being dragged into the Control Flow tab of the design pane.][02]
119119
2. Double-click the Data Flow Task to switch to the Data Flow tab.
120120
3. From the Other Sources list in the Toolbox, drag an ADO.NET Source to the design surface. With the source adapter still selected, change its name to **SQL Server source** in the **Properties** pane.
121121
4. From the Other Destinations list in the Toolbox, drag an ADO.NET Destination to the design surface under the ADO.NET Source. With the destination adapter still selected, change its name to **SQL DW destination** in the **Properties** pane.
122122

123-
![][09]
123+
![Screenshot of a destination adapter being dragged to a location directly below the source adapter.][09]
124124

125125
### Configure the source adapter
126126
1. Double-click the source adapter to open the **ADO.NET Source Editor**.
127127

128-
![][03]
128+
![Screenshot of the ADO.NET Source Editor. The Connection Manager tab is visible, and controls are available for configuring data flow properties.][03]
129129
2. On the **Connection Manager** tab of the **ADO.NET Source Editor**, click the **New** button next to the **ADO.NET connection manager** list to open the **Configure ADO.NET Connection Manager** dialog box and create connection settings for the SQL Server database from which this tutorial loads data.
130130

131-
![][04]
131+
![Screenshot of the Configure ADO.NET Connection Manager dialog box. Controls are available for setting up and configuring connection managers.][04]
132132
3. In the **Configure ADO.NET Connection Manager** dialog box, click the **New** button to open the **Connection Manager** dialog box and create a new data connection.
133133

134-
![][05]
134+
![Screenshot of the Connection Manager dialog box. Controls are available for configuring a data connection.][05]
135135
4. In the **Connection Manager** dialog box, do the following things.
136136

137137
1. For **Provider**, select the SqlClient Data Provider.
@@ -140,31 +140,31 @@ To continue the tutorial with this option, you need the following things:
140140
4. In the **Connect to a database** section, select the AdventureWorks sample database.
141141
5. Click **Test Connection**.
142142

143-
![][06]
143+
![Screenshot of a dialog box displaying an OK button and text that indicates that the test connection succeeded.][06]
144144
6. In the dialog box that reports the results of the connection test, click **OK** to return to the **Connection Manager** dialog box.
145145
7. In the **Connection Manager** dialog box, click **OK** to return to the **Configure ADO.NET Connection Manager** dialog box.
146146
5. In the **Configure ADO.NET Connection Manager** dialog box, click **OK** to return to the **ADO.NET Source Editor**.
147147
6. In the **ADO.NET Source Editor**, in the **Name of the table or the view** list, select the **Sales.SalesOrderDetail** table.
148148

149-
![][07]
149+
![Screenshot of the ADO.NET Source Editor. In the Name of the table or the view list, the Sales.SalesOrderDetail table is selected.][07]
150150
7. Click **Preview** to see the first 200 rows of data in the source table in the **Preview Query Results** dialog box.
151151

152-
![][08]
152+
![Screenshot of the Preview Query Results dialog box. Several rows of sales data from the source table are visible.][08]
153153
8. In the **Preview Query Results** dialog box, click **Close** to return to the **ADO.NET Source Editor**.
154154
9. In the **ADO.NET Source Editor**, click **OK** to finish configuring the data source.
155155

156156
### Connect the source adapter to the destination adapter
157157
1. Select the source adapter on the design surface.
158158
2. Select the blue arrow that extends from the source adapter and drag it to the destination editor until it snaps into place.
159159

160-
![][10]
160+
![Screenshot showing the source and destination adapters. A blue arrow points from the source adapter to the destination adapter.][10]
161161

162162
In a typical SSIS package, you use a number of other components from the SSIS Toolbox in between the source and the destination to restructure, transform, and cleanse your data as it passes through the SSIS data flow. To keep this example as simple as possible, we're connecting the source directly to the destination.
163163

164164
### Configure the destination adapter
165165
1. Double-click the destination adapter to open the **ADO.NET Destination Editor**.
166166

167-
![][11]
167+
![Screenshot of the the ADO.NET Destination Editor. The Connection Manager tab is visible and contains controls for configuring data flow properties.][11]
168168
2. On the **Connection Manager** tab of the **ADO.NET Destination Editor**, click the **New** button next to the **Connection manager** list to open the **Configure ADO.NET Connection Manager** dialog box and create connection settings for the Azure SQL Data Warehouse database into which this tutorial loads data.
169169
3. In the **Configure ADO.NET Connection Manager** dialog box, click the **New** button to open the **Connection Manager** dialog box and create a new data connection.
170170
4. In the **Connection Manager** dialog box, do the following things.
@@ -178,18 +178,18 @@ To continue the tutorial with this option, you need the following things:
178178
5. In the **Configure ADO.NET Connection Manager** dialog box, click **OK** to return to the **ADO.NET Destination Editor**.
179179
6. In the **ADO.NET Destination Editor**, click **New** next to the **Use a table or view** list to open the **Create Table** dialog box to create a new destination table with a column list that matches the source table.
180180

181-
![][12a]
181+
![Screenshot of the Create Table dialog box. S Q L code for creating a destination table is visible.][12a]
182182
7. In the **Create Table** dialog box, do the following things.
183183

184184
1. Change the name of the destination table to **SalesOrderDetail**.
185185
2. Remove the **rowguid** column. The **uniqueidentifier** data type is not supported in SQL Data Warehouse.
186186
3. Change the data type of the **LineTotal** column to **money**. The **decimal** data type is not supported in SQL Data Warehouse. For info about supported data types, see [CREATE TABLE (Azure SQL Data Warehouse, Parallel Data Warehouse)][CREATE TABLE (Azure SQL Data Warehouse, Parallel Data Warehouse)].
187187

188-
![][12b]
188+
![Screenshot of the Create Table dialog box, with code to create a table named SalesOrderDetail with LineTotal as a money column and no rowguid column.][12b]
189189
4. Click **OK** to create the table and return to the **ADO.NET Destination Editor**.
190190
8. In the **ADO.NET Destination Editor**, select the **Mappings** tab to see how columns in the source are mapped to columns in the destination.
191191

192-
![][13]
192+
![Screenshot of the Mappings tab of the ADO.NET Destination Editor. Lines connect columns with identical names in the source and destination tables.][13]
193193
9. Click **OK** to finish configuring the destination.
194194

195195
## Run the package to load the data
@@ -199,11 +199,11 @@ The following paragraphs describe what you see if you created the package with t
199199

200200
As the package begins to run, you see yellow spinning wheels to indicate activity as well as the number of rows processed so far.
201201

202-
![][14]
202+
![Screenshot showing the source and destination adapters with yellow, spinning wheels over each adapter and the text "29916 rows" between them.][14]
203203

204204
When the package has finished running, you see green check marks to indicate success as well as the total number of rows of data loaded from the source to the destination.
205205

206-
![][15]
206+
![Screenshot showing the source and destination adapters. Green check marks are over each adapter, and the text "121317 rows" is between them.][15]
207207

208208
Congratulations! You've successfully used SQL Server Integration Services to load data into Azure SQL Data Warehouse.
209209

‎docs/integration-services/load-data-to-sql-database-with-ssis.md‎

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -69,28 +69,28 @@ Visual Studio opens and creates a new Integration Services (SSIS) project. Then
6969
* In the middle, the design surface, with multiple tabs. You typically use at least the **Control Flow** and the **Data Flow** tabs.
7070
* On the right, the **Solution Explorer** and the **Properties** panes.
7171

72-
![][01]
72+
![Screenshot of Visual Studio showing the Toolbox pane, the design pane, the Solution Explorer pane, and the Properties pane.][01]
7373

7474
## Create the basic data flow
7575
1. Drag a Data Flow Task from the Toolbox to the center of the design surface (on the **Control Flow** tab).
7676

77-
![][02]
77+
![Screenshot of Visual Studio showing a Data Flow Task being dragged into the Control Flow tab of the design pane.][02]
7878
2. Double-click the Data Flow Task to switch to the Data Flow tab.
7979
3. From the Other Sources list in the Toolbox, drag an ADO.NET Source to the design surface. With the source adapter still selected, change its name to **SQL Server source** in the **Properties** pane.
8080
4. From the Other Destinations list in the Toolbox, drag an ADO.NET Destination to the design surface under the ADO.NET Source. With the destination adapter still selected, change its name to **SQL destination** in the **Properties** pane.
8181

82-
![][09]
82+
![Screenshot of a destination adapter being dragged to a location directly below the source adapter.][09]
8383

8484
## Configure the source adapter
8585
1. Double-click the source adapter to open the **ADO.NET Source Editor**.
8686

87-
![][03]
87+
![Screenshot of the ADO.NET Source Editor. The Connection Manager tab is visible, and controls are available for configuring data flow properties.][03]
8888
2. On the **Connection Manager** tab of the **ADO.NET Source Editor**, click the **New** button next to the **ADO.NET connection manager** list to open the **Configure ADO.NET Connection Manager** dialog box and create connection settings for the SQL Server database from which this tutorial loads data.
8989

90-
![][04]
90+
![Screenshot of the Configure ADO.NET Connection Manager dialog box. Controls are available for setting up and configuring connection managers.][04]
9191
3. In the **Configure ADO.NET Connection Manager** dialog box, click the **New** button to open the **Connection Manager** dialog box and create a new data connection.
9292

93-
![][05]
93+
![Screenshot of the Connection Manager dialog box. Controls are available for configuring a data connection.][05]
9494
4. In the **Connection Manager** dialog box, do the following things.
9595

9696
1. For **Provider**, select the SqlClient Data Provider.
@@ -99,31 +99,31 @@ Visual Studio opens and creates a new Integration Services (SSIS) project. Then
9999
4. In the **Connect to a database** section, select the AdventureWorks sample database.
100100
5. Click **Test Connection**.
101101

102-
![][06]
102+
![Screenshot of a dialog box displaying an OK button and text that indicates that the test connection succeeded.][06]
103103
6. In the dialog box that reports the results of the connection test, click **OK** to return to the **Connection Manager** dialog box.
104104
7. In the **Connection Manager** dialog box, click **OK** to return to the **Configure ADO.NET Connection Manager** dialog box.
105105
5. In the **Configure ADO.NET Connection Manager** dialog box, click **OK** to return to the **ADO.NET Source Editor**.
106106
6. In the **ADO.NET Source Editor**, in the **Name of the table or the view** list, select the **Sales.SalesOrderDetail** table.
107107

108-
![][07]
108+
![Screenshot of the ADO.NET Source Editor. In the Name of the table or the view list, the Sales.SalesOrderDetail table is selected.][07]
109109
7. Click **Preview** to see the first 200 rows of data in the source table in the **Preview Query Results** dialog box.
110110

111-
![][08]
111+
![Screenshot of the Preview Query Results dialog box. Several rows of sales data from the source table are visible.][08]
112112
8. In the **Preview Query Results** dialog box, click **Close** to return to the **ADO.NET Source Editor**.
113113
9. In the **ADO.NET Source Editor**, click **OK** to finish configuring the data source.
114114

115115
## Connect the source adapter to the destination adapter
116116
1. Select the source adapter on the design surface.
117117
2. Select the blue arrow that extends from the source adapter and drag it to the destination editor until it snaps into place.
118118

119-
![][10]
119+
![Screenshot showing the source and destination adapters. A blue arrow points from the source adapter to the destination adapter.][10]
120120

121121
In a typical SSIS package, you use a number of other components from the SSIS Toolbox in between the source and the destination to restructure, transform, and cleanse your data as it passes through the SSIS data flow. To keep this example as simple as possible, we're connecting the source directly to the destination.
122122

123123
## Configure the destination adapter
124124
1. Double-click the destination adapter to open the **ADO.NET Destination Editor**.
125125

126-
![][11]
126+
![Screenshot of the the ADO.NET Destination Editor. The Connection Manager tab is visible and contains controls for configuring data flow properties.][11]
127127
2. On the **Connection Manager** tab of the **ADO.NET Destination Editor**, click the **New** button next to the **Connection manager** list to open the **Configure ADO.NET Connection Manager** dialog box and create connection settings for the database into which this tutorial loads data.
128128
3. In the **Configure ADO.NET Connection Manager** dialog box, click the **New** button to open the **Connection Manager** dialog box and create a new data connection.
129129
4. In the **Connection Manager** dialog box, do the following things.
@@ -137,17 +137,17 @@ Visual Studio opens and creates a new Integration Services (SSIS) project. Then
137137
5. In the **Configure ADO.NET Connection Manager** dialog box, click **OK** to return to the **ADO.NET Destination Editor**.
138138
6. In the **ADO.NET Destination Editor**, click **New** next to the **Use a table or view** list to open the **Create Table** dialog box to create a new destination table with a column list that matches the source table.
139139

140-
![][12a]
140+
![Screenshot of the Create Table dialog box. S Q L code for creating a destination table is visible.][12a]
141141
7. In the **Create Table** dialog box, do the following things.
142142

143143
1. Change the name of the destination table to **SalesOrderDetail**.
144144

145-
![][12b]
145+
![Screenshot of the Create Table dialog box. S Q L code is visible for creating a table named SalesOrderDetail.][12b]
146146

147147
2. Click **OK** to create the table and return to the **ADO.NET Destination Editor**.
148148
8. In the **ADO.NET Destination Editor**, select the **Mappings** tab to see how columns in the source are mapped to columns in the destination.
149149

150-
![][13]
150+
![Screenshot of the Mappings tab of the ADO.NET Destination Editor. Lines connect columns with identical names in the source and destination tables.][13]
151151
9. Click **OK** to finish configuring the destination.
152152

153153
## Run the package to load the data
@@ -157,11 +157,11 @@ The following paragraphs describe what you see if you created the package with t
157157

158158
As the package begins to run, you see yellow spinning wheels to indicate activity as well as the number of rows processed so far.
159159

160-
![][14]
160+
![Screenshot showing the source and destination adapters. Yellow, spinning wheels are over each adapter, and the text "89748 rows" is between them.][14]
161161

162162
When the package has finished running, you see green check marks to indicate success as well as the total number of rows of data loaded from the source to the destination.
163163

164-
![][15]
164+
![Screenshot showing the source and destination adapters. Green check marks are over each adapter, and the text "121317 rows" is between them.][15]
165165

166166
Congratulations! You've successfully used SQL Server Integration Services to load data into SQL Server or Azure SQL Database.
167167

0 commit comments

Comments
 (0)