In this case, one
has to be careful about which of the servers the Task Editor brings up automatically
during configuration.
Hands-On Exercise: Creating and
Testing a Package that Uses a Transfer
Database Task
In order to follow the steps as indicated, you will need a Transfer Database Task,
the ability to make connection to the two servers, and the required permissions. In
this exercise, the pubs database on the SQL Server 2000 on a networked computer,
Computer 1 (XPHTEK in this example), will be copied over to the SQL Server 2005
Express on the Computer 2 (Hodentek in this example), on which the Visual Studio 2005
is also installed. If pubs are not available for some reason, any other database may be
used. In addition to the SQL Server 2005 Express, Computer 2 also has an SQL Server
2005 Standard Edition installed.
Step 1: Creating a Network Share on
Computer 1
As a preparation to the Transfer Database Task, a network share on Computer 1 will
be created, because this share will be needed during the transfer.
1. Create a network share (called PubsData) on Computer 1, so that the Data
folder of SQL Server 2000 is accessible from Computer 2.
This folder will be normally found at the location C:\Program Files\
Microsoft SQL Server\MSSQL for a default installation.
The following steps will be described in setting up a BI project that creates a
package containing a Transfer Database Task.
Creating a BI project and adding a Transfer Database Task.
Pages:
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164