Showing posts with label utility. Show all posts
Showing posts with label utility. Show all posts

Sunday, March 11, 2012

DTs and Buisness Intellegence

i have a bunch of dts packages..from sql2k
is there a utility to convert them to sql2005

any suggestions
daveOn Jan 30, 10:01 am, "DAVE" <dvs_...@.sbcglobal.netwrote:

Quote:

Originally Posted by

i have a bunch of dts packages..from sql2k
is there a utility to convert them to sql2005
>
any suggestions
dave


NO.
Minimal conversion is built in...depends on complexity

SQL Server 2005 Books Online:
Using the Package Migration Wizard
Known Package Migration Issues

Friday, March 9, 2012

DTS (Oracle to SQL Server 2000)

I am trying to convert an application database from Oracle to SQL Server 2000. I am using Data Transformation Services utility provided by SQL Server. I am converting data on table-by-table basis. However, whenever I convert DATE fields (form Oracle) into DATETIME fields (to SQL Server 2000), my tasks fails. Does anyone knows the reason and, more important, a solution to this problem ?Hi

I'm also working with an Oracle Database.

In my configuration it works.
I used a Transform data task and the transformation I used is a copy column.

So

Oracle:
numeric/field1, datetime/field2 >> source in Transform data task

SQL Server 2000:
numeric/field1, datetime/field2 >> destination in Transform data task

Transformations: let SQL Server do automapping, copy column.

Greetings
Jon@.s

Friday, February 24, 2012

DTExecUI - Package Execution Utility Error

Hi,

when i deploy my package using the DTExecUI thru the Package Execution Utility.when we execute the package . we are getting the following error.

The Product Levelis insufficient for component "Flat File Source(1)"

the package design is

FlatFileSource -> OlEDBDestination

what could be the solution for this?

Thanks

Jegan

You need to install SSIS on this machine.
Most likely you've installed Workstation Components, but to run packages outside of designer environment you need to install SSIS (separate checkbox on one of first setup pages).|||Thanks Michael

DTExecUI - Package Execution Utility Error

Hi,

when i deploy my package using the DTExecUI thru the Package Execution Utility.when we execute the package . we are getting the following error.

The Product Levelis insufficient for component "Flat File Source(1)"

the package design is

FlatFileSource -> OlEDBDestination

what could be the solution for this?

Thanks

Jegan

You need to install SSIS on this machine.
Most likely you've installed Workstation Components, but to run packages outside of designer environment you need to install SSIS (separate checkbox on one of first setup pages).|||Thanks Michael

DTEXec Utility

Can the DTExec Utility run a legacy DTS that is on a SQL server 2005? I have been trying to run one for weeks with no luck and can't find documentation anywhere stating whether it can or not. Only that it is DTS runs replacement.

To run a legacy DTS package, continue to use dtsrun, which is also installed with SQL Server 2005. Dtexec has no provision for running a 2000 package.

Thanks,

jkh

DTEXEC ReturnCode

Hi,

The DTEXEC Utility has the capability of returning ReturnCodes which have specific meanings e.g.

ReturnCode=3 means: The package was canceled by the user.

Is it possible to set my own ReturnCode values?

For example, my Package contains a Script Task which contains code to search a folder for a file. If the file cannot be found then I make the Script Task fail and hence the Package fails. But, when the Package is invoked by the DTEXEC utility, then the ReturnCode is always set to 1. Is it posssible to set the ReturnCode from within the Package (in, say, a Script Task in the Event Handler) to a different value?

It is necessary to be able to set custom application-specific return codes because these return codes are passed to the Batch Scheduler which alerts Operations (Support) staff in the event of failure. Meaningful (custom) ReturnCodes expedite problem solving and are (usually) mandatory in large production environments.

If it is not possible to make a Package return my own returncodes via DTEXEC then can you suggest alternative solutions, please?

Thanks.

The /CONS option is useful but not the answer. Any Ideas?

Sunday, February 19, 2012

dtexec

I understand to schedule an SSIS package to run, I need to use the dtexec utility. I want to schedule the job right within SQL. I walked through how to set up the job, but I really could not decipher the proper syntax to use as a Step.

I have the following:

dtexec /File "C:\...file.dtsx"

Is the the proper way to schedule and execute an SSIS package or is there some other way I should be doing this. The pacakge will run unattended nightly. I am using SQL Server 2005.

Thanks for the information

Hi, yes the command line syntax can be a bit daunting. But you should not have to type it out yourself...if your using SQL agent and choose the Step type of "SQl Server Integration Services Package", it will show a UI that helps you build the command line for you though you do not need to build the full command line there.

If your running outside of Agent or want to run with Agent and the step type of Command exec then use dtexecui.exe as it will also help you build the command line...and its the basis of the agent UI I mention above.

Hope that helps