dbTalk Databases Forums  

Sticky destination database name

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


Discuss Sticky destination database name in the microsoft.public.sqlserver.dts forum.



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

Default Sticky destination database name - 02-08-2005 , 06:44 PM






I build a fancy DTS package to migrate data from a source database S
to a destination database D. But, I can't touch D right now, so I
actually build the package to use destination X. Everything works.

Now, I try to use a dynamic connection to set the destination initial
catalog (aka database) to D. But, all my transform steps have the
full [X].[dbo].[tablename] path, the [X] is sticking instead of
sliding to the [D] where it belongs.

Is this a known behavior? Is it a feature? Is there a way around
this "feature"?

Thanx.

Josh


Reply With Quote
  #2  
Old   
Steffany
 
Posts: n/a

Default Re: Sticky destination database name - 02-08-2005 , 07:02 PM






Not sure if it is a feature or not, but I also just ran across this
behavior.

What I did to fix it was go into each Transform Data Task, in the
Destination Tab, in the Table name dropdown list, select the same table
name in the new destination database ([D].[dbo].[tablename]).

Hope this helps.

Steffany


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

Default Re: Sticky destination database name - 02-09-2005 , 12:41 AM



On 8 Feb 2005 17:02:02 -0800, "Steffany" <with2fs (AT) gmail (DOT) com> wrote:
Quote:
Not sure if it is a feature or not, but I also just ran across this
behavior.

What I did to fix it was go into each Transform Data Task, in the
Destination Tab, in the Table name dropdown list, select the same table
name in the new destination database ([D].[dbo].[tablename]).

Hope this helps.
Well it helps and it hurts, since I had about a dozen tables to do,
and it's kinda error prone, the way the inteface is designed (sizable
dialogs, Microsoft, please read your own standards!) It had me
mystified yesterday, until I realized (a) what had happened, and (b)
that it wasn't entirely my fumbling that had caused it.

J.



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.