Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS Package created in SQL 2008 Expand / Collapse
Author
Message
Posted Monday, September 9, 2013 3:33 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Thursday, September 11, 2014 3:32 PM
Points: 977, Visits: 3,357
Hello Everyone
I have some SSIS packages that were created in SQL 2008, I am moving all the packages to SQL 2012. What should I look for, or be aware of when I create the SQL jobs in SQL 2012 for the 2008 packages? I have already found the Provider=SQLNCLI10.1 to Provider=SQLNCLI11.1

Does anyone have a sample of the command line? The one that SQL Job creates is giving me a warning.
Here is what SQL generated:

/DTS "\"\MSDB\TestAndDev\Andrew\"" /SERVER Mistress /CONFIGFILE "\"D:\TestAndDev\SSIS Packages\Andrew\XMLConfig\TestAndDev_XMLConfig.dtsConfig\"" /WARNASERROR /VALIDATE /REPORTING E


But the Pre Execute validation is giving an error in the command line. When I execute the package, it indicates a Success, but does not get past the second step, which is a ScriptTask

Thanks in advance
Andrew SQLDBA
Post #1492931
Posted Monday, September 9, 2013 3:56 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, September 11, 2014 4:39 PM
Points: 3,462, Visits: 1,800
If I understand what you are asking what you are looking for is DTEXEC.exec at the beginning of the command.

I did a blog on creating SSIS commands here that may help you out.


Kenneth Fisher
I strive to live in a world where a chicken can cross the road without being questioned about its motives.
--------------------------------------------------------------------------------
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Link to my Blog Post --> www.SQLStudies.com
Post #1492939
Posted Monday, September 9, 2013 4:11 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Thursday, September 11, 2014 3:32 PM
Points: 977, Visits: 3,357
I think that what you have on your website is not really what I need. I am looking for a command line for pulling the package from a SQL store, or SQL Server.

/DTS "\"\MSDB\TestAndDev\Andrew\"" /SERVER Mistress /CONFIGFILE "\"D:\TestAndDev\SSIS Packages\Andrew\XMLConfig\TestAndDev_XMLConfig.dtsConfig\"" /WARNASERROR /VALIDATE /REPORTING E

The package is not executing the ScriptTask that is the second step in the package. Is there anything funky with SSIS 2012 executing 2008 C# ? Or anything else that you can think of that would cause the issue of not executing that step?

Thanks
Andrew SQLDBA
Post #1492944
Posted Monday, September 9, 2013 9:18 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, September 11, 2014 4:39 PM
Points: 3,462, Visits: 1,800
Not that I know of. Do you have the specific error?

Just a thought. If you haven't already done this you might try making a backup copy and opening the package up in the 2012 tools. It will want to upgrade it. Upgrade it and see if that fixes your problem. I know that the packages are not completely compatible between versions of Visual Studio so it isn't a big leap to think that you have to have an upgraded version to run correctly from a 2012 job.


Kenneth Fisher
I strive to live in a world where a chicken can cross the road without being questioned about its motives.
--------------------------------------------------------------------------------
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Link to my Blog Post --> www.SQLStudies.com
Post #1492977
Posted Tuesday, September 10, 2013 12:47 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:01 PM
Points: 13,720, Visits: 10,675
AndrewSQLDBA (9/9/2013)
I think that what you have on your website is not really what I need. I am looking for a command line for pulling the package from a SQL store, or SQL Server.

/DTS "\"\MSDB\TestAndDev\Andrew\"" /SERVER Mistress /CONFIGFILE "\"D:\TestAndDev\SSIS Packages\Andrew\XMLConfig\TestAndDev_XMLConfig.dtsConfig\"" /WARNASERROR /VALIDATE /REPORTING E

The package is not executing the ScriptTask that is the second step in the package. Is there anything funky with SSIS 2012 executing 2008 C# ? Or anything else that you can think of that would cause the issue of not executing that step?

Thanks
Andrew SQLDBA


You might want to open the script task in the SSIS 2012 editor and close it again, so it gets recompiled.

Which deployment model are you using in SSIS 2012?




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1493004
Posted Tuesday, September 10, 2013 4:11 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Thursday, September 11, 2014 3:32 PM
Points: 977, Visits: 3,357
Hello Everyone
I found out that one Must use BIDS 2012, or what ever name it has now, to convert the 2008 package(s) before they can be used in SSIS 2012. Not a big thing, but it does change some things.

I am not certain about the deployment methods. I have always copied the package manually and imported it into the MSDB database. What are the two new methods, and are they required? I do not like using anything "automated" to do too much on a production server.

Thanks
Andrew SQLDBA
Post #1493081
Posted Tuesday, September 10, 2013 4:38 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:01 PM
Points: 13,720, Visits: 10,675
The deployment models are they way SSIS packages are developed in SSIS 2012.
You have two models:

* the package deployment model: the unit of deployment is a single package. This is how it has always been since SSIS 2005.

* the project deployment model: packages now reside in a project. You can only deploy projects, not individual packages. You can use the new parameters and project connection managers.

More info: http://www.mssqltips.com/sqlservertip/2450/ssis-package-deployment-model-in-sql-server-2012-part-1-of-2/

ps: what's wrong with doing automated stuff on a production server? I don't like anything "manual" on a production server.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1493090
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse