dbTalk Databases Forums  

Reading UDL files in DTS package- not working!!

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Reading UDL files in DTS package- not working!! in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Patrick
 
Posts: n/a

Default Reading UDL files in DTS package- not working!! - 05-01-2005 , 07:50 PM






I have a few DTS packages in SQL Sever 7.0

Each have a Data Transfer Task with a Sybase 11 ASE database as a data
source and the SQL 7 table as a destination.

The Data source are defined using a Microsoft Data Link File (UDL), and the
actual connection is via ODBC (Merant Sybase Driver) as specified in the UDL
file. I have ticked the box which says "Always read properties from UDL
file". However, when after I have changed the UDL file to which the DTS was
set to read, the DTS when executed (using dtsrun) is still using the old
connection settings. This is unless I open up the DTS file with Enterprise
Manager's DTS designer and re-save the package? How could I fix this?



Reply With Quote
  #2  
Old   
Paul Smith
 
Posts: n/a

Default Re: Reading UDL files in DTS package- not working!! - 05-02-2005 , 01:07 AM






Are you using DSN less ODBC connections? If not you may need to set the ODBC
values in the control panel
"Patrick" <patl (AT) reply (DOT) newsgroup.msn.com> wrote

Quote:
I have a few DTS packages in SQL Sever 7.0

Each have a Data Transfer Task with a Sybase 11 ASE database as a data
source and the SQL 7 table as a destination.

The Data source are defined using a Microsoft Data Link File (UDL), and
the actual connection is via ODBC (Merant Sybase Driver) as specified in
the UDL file. I have ticked the box which says "Always read properties
from UDL file". However, when after I have changed the UDL file to which
the DTS was set to read, the DTS when executed (using dtsrun) is still
using the old connection settings. This is unless I open up the DTS file
with Enterprise Manager's DTS designer and re-save the package? How could
I fix this?




Reply With Quote
  #3  
Old   
Patrick
 
Posts: n/a

Default Re: Reading UDL files in DTS package- not working!! - 05-03-2005 , 10:47 AM



The UDL file itself is something like:

[oledb]
; Everything after this line is an OLE DB initstring
Provider=MSDASQL.1;Password=password;Persist Security Info=True;User
ID=userName;Extended Properties="DRIVER={MERANT 3.60 32-BIT
Sybase};UID=userName;DB=testDB;SRVR=DSRV0002;PWD=p assword";Initial
Catalog=testDB

Why can't my DTS package just pick up changes to this file without having to
re-open and re-save the DTS package, having ticked the correct tickbox!

"Paul Smith" wrote:

Quote:
Are you using DSN less ODBC connections? If not you may need to set the ODBC
values in the control panel
"Patrick" <patl (AT) reply (DOT) newsgroup.msn.com> wrote in message
news:ugc86DrTFHA.2756 (AT) tk2msftngp13 (DOT) phx.gbl...
I have a few DTS packages in SQL Sever 7.0

Each have a Data Transfer Task with a Sybase 11 ASE database as a data
source and the SQL 7 table as a destination.

The Data source are defined using a Microsoft Data Link File (UDL), and
the actual connection is via ODBC (Merant Sybase Driver) as specified in
the UDL file. I have ticked the box which says "Always read properties
from UDL file". However, when after I have changed the UDL file to which
the DTS was set to read, the DTS when executed (using dtsrun) is still
using the old connection settings. This is unless I open up the DTS file
with Enterprise Manager's DTS designer and re-save the package? How could
I fix this?





Reply With Quote
  #4  
Old   
Paul Smith
 
Posts: n/a

Default Re: Reading UDL files in DTS package- not working!! - 05-04-2005 , 01:30 AM



If you have changed the database in the UDL this is not reflected in the
transform task, so if the Source on the task is shown as
[database].[schema].tablename], then you need to change it in an ActiveX
script so that the [database] portion reflects the actual database being
used.

I normally have an ActiveX script that initialises this property by simply
removing the first part of a 3 part path, but only if it has 3 parts - that
stops it going wrong on the 2nd and subsequent executions

"Patrick" <patl (AT) reply (DOT) newsgroup.msn.com> wrote

Quote:
The UDL file itself is something like:

[oledb]
; Everything after this line is an OLE DB initstring
Provider=MSDASQL.1;Password=password;Persist Security Info=True;User
ID=userName;Extended Properties="DRIVER={MERANT 3.60 32-BIT
Sybase};UID=userName;DB=testDB;SRVR=DSRV0002;PWD=p assword";Initial
Catalog=testDB

Why can't my DTS package just pick up changes to this file without having
to
re-open and re-save the DTS package, having ticked the correct tickbox!

"Paul Smith" wrote:

Are you using DSN less ODBC connections? If not you may need to set the
ODBC
values in the control panel
"Patrick" <patl (AT) reply (DOT) newsgroup.msn.com> wrote in message
news:ugc86DrTFHA.2756 (AT) tk2msftngp13 (DOT) phx.gbl...
I have a few DTS packages in SQL Sever 7.0

Each have a Data Transfer Task with a Sybase 11 ASE database as a data
source and the SQL 7 table as a destination.

The Data source are defined using a Microsoft Data Link File (UDL), and
the actual connection is via ODBC (Merant Sybase Driver) as specified
in
the UDL file. I have ticked the box which says "Always read properties
from UDL file". However, when after I have changed the UDL file to
which
the DTS was set to read, the DTS when executed (using dtsrun) is still
using the old connection settings. This is unless I open up the DTS
file
with Enterprise Manager's DTS designer and re-save the package? How
could
I fix this?







Reply With Quote
  #5  
Old   
Patrick
 
Posts: n/a

Default Re: Reading UDL files in DTS package- not working!! - 05-04-2005 , 08:50 AM



Don't think this is the cause of the issue, as the DataSource is a SQL
Statement like
exec p_AStoredProc param1,param2

not [database].[schema].table

"Paul Smith" wrote:

Quote:
If you have changed the database in the UDL this is not reflected in the
transform task, so if the Source on the task is shown as
[database].[schema].tablename], then you need to change it in an ActiveX
script so that the [database] portion reflects the actual database being
used.

I normally have an ActiveX script that initialises this property by simply
removing the first part of a 3 part path, but only if it has 3 parts - that
stops it going wrong on the 2nd and subsequent executions

"Patrick" <patl (AT) reply (DOT) newsgroup.msn.com> wrote in message
news:3E380692-048A-45B9-844A-B4AB38A3751B (AT) microsoft (DOT) com...
The UDL file itself is something like:

[oledb]
; Everything after this line is an OLE DB initstring
Provider=MSDASQL.1;Password=password;Persist Security Info=True;User
ID=userName;Extended Properties="DRIVER={MERANT 3.60 32-BIT
Sybase};UID=userName;DB=testDB;SRVR=DSRV0002;PWD=p assword";Initial
Catalog=testDB

Why can't my DTS package just pick up changes to this file without having
to
re-open and re-save the DTS package, having ticked the correct tickbox!

"Paul Smith" wrote:

Are you using DSN less ODBC connections? If not you may need to set the
ODBC
values in the control panel
"Patrick" <patl (AT) reply (DOT) newsgroup.msn.com> wrote in message
news:ugc86DrTFHA.2756 (AT) tk2msftngp13 (DOT) phx.gbl...
I have a few DTS packages in SQL Sever 7.0

Each have a Data Transfer Task with a Sybase 11 ASE database as a data
source and the SQL 7 table as a destination.

The Data source are defined using a Microsoft Data Link File (UDL), and
the actual connection is via ODBC (Merant Sybase Driver) as specified
in
the UDL file. I have ticked the box which says "Always read properties
from UDL file". However, when after I have changed the UDL file to
which
the DTS was set to read, the DTS when executed (using dtsrun) is still
using the old connection settings. This is unless I open up the DTS
file
with Enterprise Manager's DTS designer and re-save the package? How
could
I fix this?








Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.