|
Home > Archive > microsoft.public.cert.mcdba > June 2002 > DTS packages
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Can someone explain this to me?
"You have been hired as a database administrator in the Seattle branch
office of a clothing manufacturer. A mainframe database at the
headquarters contains all company data. Each branch office contains an
SQL Server 2000 computer that imports regional data from the mainframe
database. The server in Seattle contains a Data Transformation
Services (DTS) package that uses OLE DB to connect to the company's
mainframe database. The DTS package extracts and transforms data about
buyers and products for that region. The DTS package then writes the
data to the SQL Server database in Seattle.
You need to configure an SQL Server computer for a new branch office
in London. You want to copy the Seattle package and modify it so that
it writes data to the SQL Server database in London. You use the DTS
Designer to modify the DTS package so that it imports regional data
from the mainframe database to the server in London. The modified DTS
package runs successfully on the server in Seattle. You save this DTS
package to the server in London, but the server in London cannot
connect to the mainframe database. You want to enable the server in
London to connect to the mainframe database. What should you do?
a. Change the connection properties in the DTS package so that the
package uses new login credentials to connect to the mainframe
database.
b. Modify the workflow in the DTS package so that the server in London
is included.
c. On the server in London, install an OLE DB provider for the
mainframe database.
d. On the server in London, delete and then re-create the DTS package.
Answer: C"
Installing an OLE DB provider? I haven't dealt with DTS that much,
but I figured that if you have SQL Server installed on a machine, the
OLE DB provider for SQL Server option is automatically available in
the DTS Designer and therefore, even a package that you bring in from
another place should be happy?
| |
| Tom Jones 2002-06-23, 6:15 am |
| For connection to a mainframe computer, you are probably using a
specialised, manufacturer-supplied OLE DB provider that isn't included in
the standard MDAC package ..
(We have the same 'problem' for accessing a Sculptor database on NT - on
every computer that needs to access the database direct we have to install
the Sculptor drivers ....)
tom.
"RK" <rkhalili@hotmail.com> wrote in message
news:2d3e4183.0205082021.3f14939a@posting.google.com...
> Can someone explain this to me?
>
> "You have been hired as a database administrator in the Seattle branch
> office of a clothing manufacturer. A mainframe database at the
> headquarters contains all company data. Each branch office contains an
> SQL Server 2000 computer that imports regional data from the mainframe
> database. The server in Seattle contains a Data Transformation
> Services (DTS) package that uses OLE DB to connect to the company's
> mainframe database. The DTS package extracts and transforms data about
> buyers and products for that region. The DTS package then writes the
> data to the SQL Server database in Seattle.
>
> You need to configure an SQL Server computer for a new branch office
> in London. You want to copy the Seattle package and modify it so that
> it writes data to the SQL Server database in London. You use the DTS
> Designer to modify the DTS package so that it imports regional data
> from the mainframe database to the server in London. The modified DTS
> package runs successfully on the server in Seattle. You save this DTS
> package to the server in London, but the server in London cannot
> connect to the mainframe database. You want to enable the server in
> London to connect to the mainframe database. What should you do?
>
> a. Change the connection properties in the DTS package so that the
> package uses new login credentials to connect to the mainframe
> database.
> b. Modify the workflow in the DTS package so that the server in London
> is included.
> c. On the server in London, install an OLE DB provider for the
> mainframe database.
> d. On the server in London, delete and then re-create the DTS package.
>
> Answer: C"
>
>
> Installing an OLE DB provider? I haven't dealt with DTS that much,
> but I figured that if you have SQL Server installed on a machine, the
> OLE DB provider for SQL Server option is automatically available in
> the DTS Designer and therefore, even a package that you bring in from
> another place should be happy?
|
|
|
|
|