Hi,

I have created DTS package in the SQLServer 2000. Now, I would like to
execute this package for multiple databases under the same sqlserver.

How can I do that?

I am trying to change it's connection's catalog property via VB.Net.
But, It seems that it's not changing and everytime I am getting results
from the same database, which I configured in DTS package. I tried to
work with Global variables. But, does not help. It's the same.

I appretiate your help.


Thank you,
Rajesh

Did you use "dynamic properties" in your DTS package?

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/


"Rajesh Patel" <rdp647 (AT) hotmail (DOT) com> wrote

Yes, I am using it. Via Dynamic properties task, I set connection's
catalog and datasource properties to global variables.



Thanks

Rajesh

Tibor Karaszi wrote:

I think, I got the solution. It was my fault. My query was referring
server and databasename in FROM clause. I removed that.

minor mistakes!!!

Thanks any way,

Rajesh

Hi,

After I made above mentioned change, package is running well from
sqlserver. But, it is not achieving desired result when I run it from
vb.net. I set global variable's values from vb.net application. It's
not picking up database name from global variable and looks like its
using database name which I specified in package itself.

Do I need to set order of step executions on vb.net application? It
works well in sqlserver though. In sqlserver, it executes
'setglobalvars' task first. When I look step collection in vb.net,
'Setglobalvars' is last in step collection.

Thanks

Rajesh

In message <1121801685.233657.4960 (AT) g43g2000cwa (DOT) googlegroups.com>, Rajesh
Patel <rdp647 (AT) hotmail (DOT) com> writes
The package should include a workflow constraint to ensure the tasks
execute in the correct order. The order in the collection is not
relevant if constrained properly through workflow.

A couple of other points-

A connection needs to be closed for any changes to take effect, so
either make the changes before any other tasks use it, or ensure the
last task to use it, before the change, has the Close connection on
completion property set.

Some tasks, in particular the DataPump and DDQ, catch people out as by
default the UI will include the DB in properties such as
SourceObjectName and DestinationObjectName.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org