-------------------------------------------------------------------
:::: Great Indian Developer Summit 2009 - GIDS .Net ::::
:::: 24 April 2009 ::::
:::: J N Tata Auditorium, IISc, Bangalore ::::
:::: http://www.developersummit.com ::::
-------------------------------------------------------------------
Dear Group members,

The economic downturn will run out of steam trying to outdo the 'ready
and waiting' software professional. Packed with premium knowledge,
action plans and advise from been-there-done-it veterans, creators...

Hi,

Any idea on using schtasks.exe in BAT file to auto-executing the SSIS?

I have issue in putting the value after /TR as below:
"C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTExec.exe" /File
"D:\Source\A.dtsx" /DECRYPT ABC /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/REPORTING V /CONNECTION DestinationConnectionOLEDB;"\"Data Source=.;Initial
Catalog=Dev;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto
Translate=false;\""

it only allows to key in D:\Source\A.dtsx instead of above statement.

Please advice
thank you.

GL

Hi Russel!

Can't use it, need to do it in the flow. I was thinking of merging the 16
bytes into 8 by xoring the two Int64 together, would be sufficient for most
(all?) applications.

Thanks,
Gorm

"Russell Fields" nomail.com> wrote in message
news:#7P7HCIZJHA.5312@TK2MSFTNGP02.phx.gbl...

I am trying to run a SSIS package from Visual Studio on my machine. This
package is to connect to a database but I am getting this error:

The AcquireConnection method call to the connection manager failed with
error code.

What might be causing this error?

Toni,

DTS is still available at SQL Server 2000 level for SQL Server 2008, but not
enthusiastically supported.
http://msdn.microsoft.com/en-us/library/cc707786.aspx

There are a few steps to go through, but (at least on SQL Server 2005) it
all works just fine. Therefore, it is still being supported for 2008, and
the documentation on how to do it is a bit better than the 2005 docs.

RLF

"Toni" discussions.microsoft.com> wrote in message
news:23DAE0E6-F4C3-4A8A-9BA0-14900E485ECC@microsoft.com...

I think, that I have to do something wrong. In periodicaly running updates,
at the end of the transformation, I usually use OLE DB Destination and if the
INSERT fails (usually because of the PK conflict), row is redirected to the
error output and there the OLE DB Command make UPDATE of this row to the DB.

This technique working well, but!!! -> In the UPDATE command is not possible
use named parameters (I have to use UPDATE myTable SET column1 = ? WHERE
column2 = ?). In case I have tables with a few columns, that is no problem.
But I often transform data tables from the AS400 DB and there are 140 columns
with 8 primary keys and with only 8 characters in the column name. Which
means, it is very unclear (not well arranged). On one side I have columns
from AS400 DB2 named for example GLPMJ, GLGTGF, GLRUID, etc.. on other side
unnamed parameters Param_0, Param_1, Param_3. etc....

My questions are:
1) Is there way to use named parameters in the OLE DB Command?
2) Is there another way to perform update command based on keys in the
destination table??

Thanks alot for the help.

Hi, I wanted to make sure you were all aware of these upcoming events.
There is a seminar in Predictive Analytics on Oct. 24-25 in DC, and in
San Francisco Nov 6-7. This is intensive training for managers,
marketers, and IT people who need to make sense of customer data to
predict buying behavior, profit, etc. Past attendees have given rave
reviews.

You can find more info at http://www.predictionimpact.com/predictive-analytics-training.html,
e-mail training@predictionimpact.com, or call (415) 683-1146.

thanks --Elise Johnson, Prediction Impact

New to SSIS so bear with me....

I have migrated a 2000 DTS package to a 2005 SSIS package. The migration
wizard converted all DTS tasks(20 tasks) to an "EXECUTE DTS 2000 PACKAGE
TASK" control flow item(20 control flow tasks). The task is a simple extract
from an Excel worsheet and load into a SQL 2005 database table.

I did not create the original DTS package and am noticing that even though
the source of all tasks is the same Excel file a new Data Source/Connection
Manager was created for each "read" from the same Excel file(Needless to say
you can imagine how many connection managers the package has). The migration
wizard of course re-created all the Data Sources/connection managers just
like they existed in DTS 2000. The wizard worked great from that standpoint.

Now the problem, I would like to clean up the SSIS package and basically
have all 20 Control Flow tasks reference the one Excel Data Source/Connection
Manager; however, when I edit the control flow task and get into the DTS 2000
Package Designer I am unable to select the same connection when I choose the
Existing Connection radio button. I hope this makes sense. The drop-down
box does not show me all connections to pick from.

Basically, I want to have one connection to Excel and have all twenty(20)
control flow tasks reference this one Data Source/Connection manager.

What specific things have to do, that I will be able referencing my own
assembly in the script editor in DataFlow ScriptComponent.

I Strongly signed my asembly, install that into the GAC, but I cannot see it
in the list of asseblies in the ScriptComponent references. There is nio
possibility to browse for that assembly.

Thanks for answer

Mirek

HI

I want to change the source table using the DSO scripting .

For example the particular dimension has the source table as TABLE1

using the DSO scripting i want to change the source table to TABLE2

Can you please any help me regarding this

Thanks in advance

santosh