Can Copying connections in dts packages cause errors? 2

[uncgis]

Instead of creating a new connection in a DTS package to add another table...i simply copied a connection and pasted it beside it...then i changed the name back to an existion connection under connection properties...needless to say, whenever i go uder disconnected edit >> Connections..i have
Connection 1
Connection 2
Connection 1 Copy
COnnection 2 Copy
Connection 1 Copy 2
Connection 2 Copy 2
Connection 3
Connection 4

Now the scheduled DTS package fails and i am not sure if it has something to do with the connections I am not using (all the copied connections)

Does anyone know if this would causes errors?
Does anyone know how to delete the copied connections?

Thanks

 

[yksvaan]

Causes errors?"
Not unless you have deleted a connection and you have a task using that connection. Check what connections your tasks use.

Can't you just righ-click the icon and choose delete ?

Cheers

 

[gradley]

When you change a copied connection to an existing connection name, it is actually referencing that initial connection. This is important to understand because if you change properties of the connection it changes them all. If you truely want a separate connection, you should make the connection names different.

If you want to get rid of the other connection names you are no longer using but still appear in the dropdown of available connections then perform the following:

1. Add another connection
2. Reference the un-used connection
3. Delete this new connection
4. The un-used one should now be gone.

Good Luck!

 

[yksvaan]

Thanks gradley for pointing out that properties are about connections not icons.

uncgis, one thing. You don't have to have multiple connections if you need to transform several tables between the same source and destination. You can just make multiple Transform tasks. When you run it, dts tries to run them all at the same time though. If it's ok, fine, but else you can define (in the task's Workflow properties) a success precedence order for them. This is not so self-explanatory(my new favourite word, do you know a shorter expression) visually it is shown as green arrow going to the opposite direction. So sometimes I too tend to make many connections, if I have more than three transform.

If you have to look at complex packages somebody else has made, the arrows may not mean order of execution just the way one would imagine at first.

Cheers


[blue]Backup system is as good as the latest recovery[/blue]

 

[yksvaan]

I must add, that I quite didn't get what the actual problem was, but who cares. I'm trying to make "lost connections", but where are they when they are needed..

Cheers


[blue]Backup system is as good as the latest recovery[/blue]

 

[Jozopiso]

Hi Everybody,

i'm transfering one big SQLscript into DTS package. Here is my problem. Whem i'm puting 'Create procedure' from that script into stored procedures, it always tells me that I didn't declare values(@WorkForce INT,@Recr_ID INT)...here is code from that script:

-- Create Import Procedures
if exists (select * from sysobjects where id = object_id(N'Truncate_import_tables') and OBJECTPROPERTY(id, N'IsProcedure') = 1)
drop procedure [Truncate_import_tables]
GO

SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO

CREATE PROCEDURE Truncate_import_tables
AS

truncate table Import_Person
truncate table Import_PersonJob
truncate table Import_PersonEducation
truncate table Import_PersonSkill


GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO

if exists (select * from sysobjects where id = object_id(N'Import_temp_data') and OBJECTPROPERTY(id, N'IsProcedure') = 1)
drop procedure [Import_temp_data]
GO

SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO

CREATE PROCEDURE Import_temp_data
@WorkForce INT,
@Recr_ID INT
AS
begin transaction Import

declare @id_person int
declare @id_othercat int
......
.....
.....
etc

AND I WOULD LIKE TO CALL THOSE "PROCEDURES" FROM STORED PROCEDURES LIKE:
-- Create Import Procedures


SET QUOTED_IDENTIFIER ON

SET ANSI_NULLS ON

exec Truncate_import_tables



SET QUOTED_IDENTIFIER OFF

SET ANSI_NULLS ON





SET QUOTED_IDENTIFIER ON

SET ANSI_NULLS ON


exec Import_temp_data

SET QUOTED_IDENTIFIER ON

SET ANSI_NULLS ON

THANX VERY MUCH

 

[yksvaan]

So you have parameters in creating proc
CREATE PROCEDURE Import_temp_data
@WorkForce INT,
@Recr_ID INT

But not give parameter values when you call it
exec Import_temp_data

I think you should start a new thread about this.

Cheers


[blue]Backup system is as good as the latest recovery[/blue]

 

[uncgis]

thanks for all the posts....gradley's post worked out for me...thanks again