Jobs in SSIS

Hi All,
How many jobs we can run parallelely in SSIS.
Thanks in Advance....

Actually SSIS doesnt put any limit on number of jobs which can parallely execute but practically it depends on max worker threads
see
http://visakhm.blogspot.in/2011/06/sql-server-agent-job-issues-2.html
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Similar Messages

How do I automatically backup SQL Agent jobs and SSIS packages on the mirror daily?

I have seen this question asked before but I could not find a satisfactory answer. What is the best solution to get your SQL Agent jobs/schedules/etc. and your SSIS packages on the mirror server? Here's the details:
Server A is the principal with 2 DBs mirrored over to server B. Everything is fine and dandy, DBs are synched and all good. In Disaster Recovery testing, we need to bring up server B, which now will serve as the principal. Server A is inaccessible. Now,
we need all our jobs that are setup in server A to be in server B, ready to go, but disabled. We also need all our SSIS packages properly stored. Yes, we store our packages in the MSDB in server A.
Now, I can see a few answers coming my way.
1- Backup the MSDB to server B. When you bring server B up as principal in DR, restore the MSDB. All your jobs,schedules,steps, SSIS packages will be there. Is this possible? Can this be done on server B without rendering it incapable of serving as the principal
for the mirrored DBs? My fear with this option is that there may be information in the MSDB itself about the mirroring state of the DBs? Or is all that in the Master DB? Have you tried this?
2- Right click each job, script them out, re-create them on server B... No, thank you very much. :) I am looking for an AUTOMATED, DAILY backup of the jobs and SSIS packages. Not a manual process. Yes, we do change jobs and packages quite often and doing
the job twice on two servers is not an option.
3- Use PowerShell.. Really? Are we going back to scripting at the command prompt like that, that fast?
Since I fear option number 3 will be the only way to go, any hints on scripts you guys have used that you like that does what I need to do?
Any other options?
Any help GREATLY appreciated. :-) I can be sarcastic but I am a good guy..
Raphael
rferreira

I would go with option number 3. Once you have a script simple run it....
param([string]$serverName,[string]$outputPath)
function script-SQLJobs([string]$server,[string]$outputfile)
[reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo") | Out-Null
$srv = New-Object Microsoft.SqlServer.Management.Smo.Server("$server")
$db = New-Object Microsoft.SqlServer.Management.Smo.Database
$scrp = New-Object Microsoft.SqlServer.Management.Smo.Scripter($srv)
$scrp.Options.ScriptDrops = $FALSE
$scrp.Options.WithDependencies = $TRUE
$jobs = $srv.JobServer.get_Jobs()
$jobs=$jobs | Where-Object {$_.Name -notlike "sys*"}
foreach($job in $jobs)
$script=$job.Script()
$script >> $outputfile
"GO" >> $outputfile
---script-SQLJobs "SQLSRV12" "C:\Jobs\test.txt"
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Blog:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance

SQL SERVER AGENT JOB ERROR - SSIS PACKAGE

Hi ,
I have a SQL server agent job which runs SSIS package as the daily job. The SSIS package contains multiple child package. Its a master package which calls other SSIS package. The master package calls 23 SSIS packages, few of the packages runs in parallel.
I am getting the below 2 different errors more frequently. It fails only in the production server, I scheduled the job in UAT server, it did not fail. Also when we run the master package with out sql agent job, it did not fail.
Error 1 :
R6025 - pure virtual function call. The return value was unknown. The process exit code was 255. The step failed.
Error 2 : The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.
We tried browsing for the answers ,no luck. It failing in live , so we need to run the package manually in live server every time.
Please help me to resolve this issue. Thanks in advance.
Regards,
Dhivya Sivakumar

Hi Vijeth,
Thanks for your reply.
1) Run the Package manually and check whether it runs successfully. -
No Failures. Package completed succesfully
2) If Step 1 is successful,
a) Point the same package to the UAT database and run it and check whether it runs successfully or not. -
We tried to schedule the package almost for 1 month. No failures in UAT.
b) In UAT database, point to the Production database and run the package. - I am not sure, if i can do this.I will try and let you know the result.
These steps will help us identify whether the problems lies within the package or the Environment.
3) Run the Package manually in production Environment using dtexec utilily. -
No Failures. Success.
4) Check the ID used to run the SQL Agent job and modify to an account with elevated permissions or GRANT more permissions to the existing ID. -
The account used currently is having all the privileges. Its the most powerful user in live DB.
Regards,
Dhivya S

Execute jobs running SSIS package

I'm testing a domain login that will have the permissions to run a job that will execute an SSIS package transferring data from DB123 to DB456 in SQL Server 2008.
This is what I have so far:
1) Create login with a domain test account (domain\xyz)
2) Create job with Owner as SA. SA account login is disabled.
3) Job calls an SSIS package, does not have a schedule and meant to be called from a SP from the front end app. So, essentially on demand.
4) Besides public on the databases mentioned below, domain\xyz account also has the following db permissions:
a) db_datareader, db_datawriter on DB123
b) db_datareader, db_datawriter on DB456
c) db_ssisadmin, db_ssisltduser, db_ssisoperator, SQLAgentOperatorRole, SQLAgentReaderRole, SQLAgentUserRole.
The issues:
Issue #1: When I login to SSMS as domain\xyz and execute
exec msdb..sp_start_job 'TestPermJob', I get the following errors
Msg 229, Level 14, State 5, Procedure xp_sqlagent_is_starting, Line 1
The EXECUTE permission was denied on the object 'xp_sqlagent_is_starting', database 'mssqlsystemresource', schema 'sys'.
Msg 229, Level 14, State 5, Procedure xp_sqlagent_notify, Line 1
The EXECUTE permission was denied on the object 'xp_sqlagent_notify', database 'mssqlsystemresource', schema 'sys'.
Before I start granting those permissions explicitly to a role and assign the role to the login, I thought msdb SQLAgentOperatorRole should allow the execution of jobs, doesn't it?
Issue #2: As domain\xyz, I cannot see any jobs on SQL Server Agent. Again, I thought granting msdb SQLAgentOperatorRole should be sufficient to do that.
Please help. Thanks.

Before I start granting those permissions explicitly to a role and assign the role to the login, I thought msdb SQLAgentOperatorRole should allow the execution of jobs, doesn't it?
Issue #2: As domain\xyz, I cannot see any jobs on SQL Server Agent. Again, I thought granting msdb SQLAgentOperatorRole should be sufficient to do that.
Hi Ami,
According to your description, in theory, SQLAgentOperatorRole is the most privileged of the SQL Server Agent fixed database roles. It includes all the permissions of SQLAgentUserRole and SQLAgentReaderRole. Members of this role can also view properties
for operators and proxies, and view all jobs on the server.
I do a test in SQL Server 2012, if we create a login name, and create a user for this login, then configure this user to
add a SQL Server Agent fixed database role(SQLAgentOperatorRole) under
Database role membership for: msdb.
When we login the SQL Server instance via this login name, we can check all jobs under SQL Server Agent. So I recommend you check if you
add a SQL Server Agent fixed database role successfully. For more information, you can review the following
article.
http://www.mssqltips.com/sqlservertip/1041/sql-server-agent-fixed-database-roles/
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL Agent job step - SSIS package - adding a config file - will it override the one that the package specifies?

If I setup a job step to run a package and set the config file location on the "Configurations" tab, will that override the config file that the SSIS package is configured to use? Or is this a "cumulative" type configuration option?
I typically have my config file mixed in with my project files, but that path wont exist on the server.

Hi Shiftbit,
ETL vs ELT is right.
In SSIS 2005, the DTExec utility loads and runs the package, events occur in the following order:
The package file is loaded.
The configurations specified in the package at design time are applied in the order specified in the package (except for Parent Package Variables).
Any options specified from the command line are applied. Any configurations specified on the command line overwrite the current values; however, they do not trigger a reload of the configurations if a changed value impacts a configuration dependency. For
example, if the connection string used for SQL Server configurations is updated from the command line at run time, the package will still retain any other values from the design-time SQL Server configuration database.
Parent Package Variable Configurations are applied.
The package is run.
In SSIS 2008 and higher, utility loads and runs the package, events occur in the following order:
The dtexec utility loads the package.
The utility applies the configurations that were specified in the package at design time and in the order that is specified in the package. (The one exception to this is the Parent Package Variables configurations. The utility applies these configurations
only once and later in the process.)
The utility then applies any options that you specified on the command line.
The utility then reloads the configurations that were specified in the package at design time and in the order specified in the package. (Again, the exception to this rule is the Parent Package Variables configurations). The utility uses any command-line
options that were specified to reload the configurations. Therefore, different values might be reloaded from a different location.
The utility applies the Parent Package Variable configurations.
The utility runs the package.
So, we can see that no matter we use SSIS 2005 which applies the Configurations once or use SSIS 2008 (or higher) which applies the configurations twice, the configurations specified in the command line will affect and not be overwritten by the configurations
specified at design-time.
Reference:
http://technet.microsoft.com/en-us/library/ms141682(v=sql.110).aspx.
Regards,
Mike Yin
TechNet Community Support

Sql server agent job with SSIS

Hello Experts
i have a sql server agent job that has four steps in tsql,ssis,tsql and tsql orders. the job run automatically every night and i copy paste the error message right here, any ideas please:
Date
1/27/2014 7:30:00 AM
Log
Job History (test [Mon-Fri AM])
Step ID
1
Server
server1
Job Name
name [Mon-Fri AM]
Step Name
step one
Duration
00:34:33
Sql Severity
0
Sql Message ID
0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted
0
Message
Executed as user x\serveragent. The step was cancelled (stopped) as the result of a stop job request.

you can try default trace / event viewer to check if there is any entry on same .
How to read default trace in sql server
Thanks Saurabh Sinha
http://saurabhsinhainblogs.blogspot.in/
Please click the Mark as answer button and vote as helpful
if this reply solves your problem

Errors in job scheduled SSIS package

A job scheduled for SSIS package failed with the below errors:
Microsoft (R) SQL Server Execute Package Utility Version 10.50.4321.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started: 5:00:02 AM
Error: 2015-01-02 05:06:39.25
Code: 0xC0202009
Source: Data Flow Task OLE DB Destination [46]
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
Error code: 0x80004005. An OLE DB record is available.
Source: "Microsoft SQL Server Native Client 10.0"
Hresult: 0x80004005
Description: "Could not allocate a new page for database because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary
space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.". End Error Error: 2015-01-02 05:06:39.42
Code: 0xC0209029
Source: Data Flow Task OLE DB Destination [46]
Description: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "input "OLE DB Destination Input" (59)"
failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (59)" specifies failure on error. An error occurred on the specified object of the specified component. There may be
error messages posted before this with more information about the failure.
End Error Error: 2015-01-02 05:06:39.44
Code: 0xC0047022
Source: Data Flow Task SSIS.Pipeline
Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "OLE DB Destination" (46) failed
with error code 0xC0209029 while processing input "OLE DB Destination Input" (59). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow
task to stop running. There may be error messages posted before this with more information about the failure.
End Error Error: 2015-01-02 05:06:39.48
Code: 0xC02020C4
Source: Data Flow Task Flat File Source [1]
Description: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.
End Error Error: 2015-01-02 05:06:39.50
Code: 0xC0047038
Source: Data Flow Task SSIS.Pipeline
Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Flat File Source" (1) returned
error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error
messages posted before this with more information about the failure.
End Error Error: 2015-01-02 05:16:23.49
Code: 0x00000000
Source: Execute SQL Task 1
Description: Could not allocate space for object 'bo.TLE'.'PK_new' in database because the 'PRIMARY' filegroup is full. Create disk space
by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
End Error Error: 2015-01-02 05:16:23.70
Code: 0xC002F210
Source: Execute SQL Task 1 Execute SQL Task
Description: Executing the query "Sp_load" failed with the following error: "Warning: Null value is eliminated by an aggregate
or other SET operation.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
End Error DTExec: The package execution returned DTSER_FAILURE (1).
Started: 5:00:02 AM
Finished: 5:16:27 AM
Elapsed: 984.928 seconds. The package execution failed. The step failed.
Please help!!!!

Hi,
Based on the error message” Could not allocate a new page for database because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth
on for existing files in the filegroup”, we can know that the issue is caused by the there is no sufficient disk space in filegroup 'PRIMARY' for the database.
To fix this issue, we can add additional files to the filegroup by add a new file to the PRIMARY filegroup on Files page, or setting Autogrowth on for existing files in the filegroup to increase the necessary space.
As to the issue that the job executed successfully for the next run when executed, I think it can be caused by someone or something had made something to increase the space.
The following document about Add Data or Log Files to a Database is for your reference:
http://msdn.microsoft.com/en-us/library/ms189253.aspx
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SSIS Package "running" in Job History?

My first post to Technet fora: Hello to everyone!
Last March our DW-system was migrated from SQL Server 2005 to SQL Server 2008 R2. Several SQL Server Agent jobs using SSIS packages were also migrated. The packages were converted from 2005 to 2008 with Visual Studio conversion tools.
After the migration several (but not all) of these jobs show a peculiar behavior in 'View Job History'.
As you can see the job history consists of two rows. But the lower one - from Execute Package Utility - has the green 'arrow head', as if it were still running.
In the Selected Row Details Pane, however, everythig seems to be ok:
Message
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.2500.0 for 64-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started: 8:00:02
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 8:00:02
Finished: 8:00:03
Elapsed: 1.482 seconds
Is this something to be concerned about? The job seems to work just fine (a simple sql query, results to flat file).

Welcome to the fora :)
Strange, everything indicates the job finished, except for that little icon.
I would ignore it and classify it as a visual glitch, but I understand it can be annoying.
MCTS, MCITP - Please mark posts as answered where appropriate.

I want to run SSIS package every time based on last time job processed data time.........

Hi all,
i have SSIS package ..its needs run every day .for that we were schedule a job for ssis..
but we need when package going to run that time we have to take data, besed on last time processed date..for that am using msdb data base to get process date ..but am not yet schedule a job am going to do 1st time..
insde the package am using this query using execte sql task
SELECT CASE WHEN DateDiff(Day, CONVERT(DATETIME, LEFT(MAX(H.run_date), 8)), GetDate()) = 0 THEN 30 ELSE DateDiff(Day, CONVERT(DATETIME, LEFT(MAX(H.run_date), 8)), GetDate()) END AS Dates
FROM dbo.sysjobhistory AS H INNER JOIN
dbo.sysjobs AS J ON H.job_id = J.job_id
WHERE (H.run_status = 1) ..
if job already ran means its was working fine.if job not yet scheduled means its giving error...
pandiyan

Try this one on:
SELECT COALESCE(dates,fallBack) AS dates, name
FROM (
SELECT 30 AS fallBack
) b
LEFT OUTER JOIN (
SELECT CASE WHEN DateDiff(Day, CONVERT(DATETIME, LEFT(MAX(H.run_date), 8)), GetDate()) = 0 THEN 30
ELSE DateDiff(Day, CONVERT(DATETIME, LEFT(MAX(H.run_date), 8)), GetDate())
END AS Dates,
j.name
FROM dbo.sysjobhistory AS H
INNER JOIN dbo.sysjobs AS J
ON H.job_id = J.job_id
WHERE H.run_status = 1
GROUP by j.name
) a
ON b.fallBack = b.fallBack
You might want to consider filtering on j.name or j.job_id to get the info for the specific job.

SSIS calling from Agen Job

i have SSIS to create Excel from SQL Query. Once Excel created uploading to FTP Site, Using Script task
When i run SSIS it works fine able to upload new file to ftp site without error. but when i run as SQL Agent , job runs successful but file is not get uploaded.
In SQL Job, calling SSIS from file system and using my id it has admin right and but not on ftp, for ftp i am hard coding user and pwd in script task.
I am assuming, when i run job, SSIS Script task is using hardcoded userid and pwd not my id .
Any reason?

Hi Vaishu,
Since the package works fine in the BIDS, I suggest that you create a SQL Server Agent proxy account to execute the job. The proxy account should base on the credentials that you use to log onto the Windows operating system. This can help us to check whether
it is a permission issue on the FTP server. For more information, please see:
http://technet.microsoft.com/en-us/library/ms190698(v=sql.105).aspx
If it is not the case, try Visakh’s suggestion to re-install the package with setting the protection level to rely on server storage.
If the issue persists, enable logging for the package as Arthur mentioned, and get the error message for further analysis.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

How do I run a full process from SSIS ???

Hi all
I run BPC 5.1 SP3, and I need to automate a series of jobs, but the system is giving me problems and I hope someone can help out.
I need to automate a full optimize and then a full process of our AppSets.
I know that in SP3, the Appsets are taken offline for the full optimize and are then left offline, so in-between I run the "SystemAvailableTask" to set the Appsets back online.
Additionally, all dependencies are removed from the FACT table for the optimized AppSets, which are only rebuilt by performing the full process afterwards.
Anyway, the problem I have is that the optimize is running quite happily from SSIS, as is the SystemAvailableTask.
Up to this point in the job, everything works as intended, so I now have a fully optimized Appset, which is available for users to access.
However, the Full Process job then fails.
I have run the Full Process as a standalone job from SSIS and it takes 2m36s to run, but fails to rebuild any dependencies.
When I ran it from the SAP Admin program, it took 9m57s to run and rebuilt everything correctly.
I am currently only offered 1 option in the SSIS package, which is to run a Full or an Incremental process, so I select Full.
However, on the right-hand side, there are various other options available (such as bApplicationProcess, PROCESSMODE (set to "3"), PROCESSOPTION (set to "1"))
Should I be changing any of the settings on the right to make the job run properly, or should I be doing it differently.
Obviously, I need to make this work from SSIS, as I can't schedule a full process any other way, so I would be extremely grateful for any help that you can offer.
Thanks
Craig
Edited by: Craig Aucott on Aug 25, 2009 10:21 AM

The easiest way to do this is to write a Tuxedo server (i.e., using only
ATMI and no CORBA stuff) that does the following:
1.) In tpsvrinit(), the last thing that it should do is a tpacall to the
service contained in this server (and nowhere else) with the TPNOREPLY
flag.
2.) In the method that implements the service, do your database work, sleep
for a little while, do another tpacall to itself with the TPNOREPLY flag,
and return.
Hope this helps,
Robert
Ram Ramesh wrote:
Hello folks:
How can I run a background process that runs under WLE's control.
What I am looking for is a way to have a process that runs in an
infinite loop and polls the database to see if there is any background
work that needs to be done. But I still want the process to be managed
by WLE for fault tolerance.
Thanks,
Ram Ramesh
[email protected]

Management Studio Fails when added Integration Services step to SQL Server Agent Job

Hi,
I have two new servers I've setup with Windows Server 2012, SQL Server 2012 SP1, Visual Studio 2012 SP4. I've previously been on SQL 2008 and VS 2008 so this is new to me.
I am finding SSMS is throwing an exception on both machines when i do the following:
1. Go to SQL Server Agent | Jobs
2. Create a new Job.
3. Select Steps and click New Step
4. Change the job type to SQL Server Integration Services Package.
Following error occurs:
TITLE: Microsoft SQL Server Management Studio
The type initializer for '<Module>' threw an exception. (SqlManagerUI)
ADDITIONAL INFORMATION:
The C++ module failed to load.
(DTEParseMgd)
Index was outside the bounds of the array. (DTEParseMgd)
I also find if I take an existing job with SSIS package steps and attempt to edit those steps the same message appears. This issue happens on both my servers as they have been configured almost identically. This doesn't occur when selecting any other job
type.
I've also tried installing cumulative update 8 in a hope that this may fix it but with no success.
As my entire environment is based around SQL Agents running SSIS i'm a little bit concerned, especially since I have some tight deadlines getting these servers running.
I have found nothing relating to this issue. Any help greatly appreciated.
Simon
Below is the detailed error message:
===================================
The type initializer for '<Module>' threw an exception. (SqlManagerUI)
Program Location:
   at Microsoft.SqlServer.Management.SqlManagerUI.DTSJobSubSystemDefinition.Microsoft.SqlServer.Management.SqlManagerUI.IJobStepPropertiesControl.Load(JobStepData data)
   at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.UpdateJobStep()
   at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.typeList_SelectedIndexChanged(Object sender, EventArgs e)
   at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
   at System.Windows.Forms.ComboBox.set_SelectedItem(Object value)
   at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.InitializeStepCombo()
   at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.InitializeData()
   at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.OnInitialization()
   at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.SetView(Int32 index, TreeNode node)
   at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.SelectCurrentNode()
   at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.InitializeUI(ViewSwitcherTreeView treeView, ISqlControlCollection viewsHolder, Panel rightPane)
   at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument doc, IServiceProvider provider, ISqlControlCollection control)
   at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(ISqlControlCollection control, IServiceProvider provider)
   at Microsoft.SqlServer.Management.SqlManagerUI.JobSteps.editJobStep_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.RunDialog(Form form)
   at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   at System.Windows.Forms.Form.ShowDialog()
   at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
===================================
The C++ module failed to load.
(DTEParseMgd)
Program Location:
   at <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* )
   at .cctor()
===================================
Index was outside the bounds of the array. (DTEParseMgd)
Program Location:
   at _getFiberPtrId()

Hi,
I hadn't installed CU3 however as a test i tried installing CU4 and this didn't help. Since my first emails i have more issues that have brought a complete hault to the upgrade project.
If i double click on a package to run it manually I basically get the same issue. This means i have no way of running any packages except throught VS.
I've also found that regardless of the order of the software installs it still fails. It's related to SP1 of SQL and SP4 of VS.
I'm on Server 2012. When install in the following order SQL 2012, SQL SP1, VS2012, BIDS, VS SP4 i have no problem until VS SP4 is installed. If i install VS SP4 then BIDS it also fails at the last step. If i install all the VS and BIDS software first, then
SQL then SQL SP1 it fails at the SQL SP1 step.
This means i could actually install everything and either ignore the SQL SP1 or the VS SP4 and i'd be fine however this is not really a solution as i will never be able to patch the software and once live this is very dangerous.
I am still surprised there is no obvious solution to this. I'm only installing MS software on a fresh box and only installing 5 pieces of software (including the SPs). I would have though if this was an issue others would have come across it too.
Has anyone else installed all these components and got them working on the same OS. I believe early on in my testing i installed these in Windows Server 2008 and didn't have the issue.
Regards.
Simon.

SSIS Package configuration.

The SSIS packages is developed using BIDS 2008 and Database SQL Server 2008 R2.The package was developed in local box/Developement box and since the
connection string is pointing to local box , it works fine and data got loaded into the target tables.
When the SSIS packages is moved from Dev box to Pre Production or Production box , the package need to be modified since the database connection string
of local is different from Prod box.
To achieve the above process xml configuration has been done which contains the connection string details, but xml is pointing from the dev box path which might not exists in the prod box, so the package need to be open in Prod box and modify the xml file
path again, which the Client is not suppose to do..
To avoid that an Environment variable need to be created which will contain the xml path.
But xml is not that much secure compare to database configuration. So they advice us to configure by SQL Configuration.
The Configuration table will be created in the Db and with the help of SQL Job , the SSIS package will be scheduled, but if the tomrrow the database server
changes the package need to re open again and modify the connection string for the configuration tables.
Could you please suggest the best possible solution for SSIS package configuration when the User move the package from Dev box to Prod Box
with least possible modification.

Hi SubhadipRoy,
Just adding to ltz's suggestion. SSIS provides several options for handling package configuration values such as environment variables, XML files, registry settings, and a table in a SQL Server database. We can store the package configuration parameter values
in a SQL Server database table, then use those stored values when executing the package.
As per my understanding, I think this method is a better solution. Because when we move the package from Dev box to Production box, we can directly use simple T-SQL commands such as INSERT, UPDATE and DELETE to change the configuration data without changing
the package.
For more information about SQL Server Integration Services SSIS Package Configuration, please refer to the following blog:
http://www.mssqltips.com/sqlservertip/1405/sql-server-integration-services-ssis-package-configuration/
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Call edq from ssis

Hi Folks, I am in the middle of EDQ Proof of Concept. I am creating a Microsoft SQL Server Integration Service (SSIS) package to call EDQ. I have create a batch (***.bat) that calls the EDQ job to run my Data Quality job. What would be the best way to call the job from SSIS would a web service be better than calling a bat file?
Thanks
Paul

That depends if you are processing large batches of data, or processing either individual requests or small batches (up to 1000 or so records).
If you are processing large batches, I would call an EDQ batch job using the command line interface (as you are presumably doing now), handing over the data via a shared DB or a text file.
If you are processing individual requests or small batches, I would recommend using EDQ's real-time interface (either JMS or Web Services).
For more info, see the Integration Essentials.

Sql server job failing some times and suuccessful some time, even when it should run succesful

Hi Experts,
I got stuck with some issue....please help me resolve
1.I created job -> calling SSIS package
2. In SSIS package ->
(I) firstly i have zip file container
(II)second i have Execute process taskk editor - here i am doing unzip - in side On query cancel i have package failure if correpted file comes.
(III) loading into table using bulk insert
Problem:
When i run the job it's working fine most of the times.
But some time job executing still Execute Process taskk editor and after that job is getting canceld as follows"The job was stoped prior to completion by (unknown)" even through i have proper file(which is gettng unzip manualy).
Please help me to resolve this issue...

What is the SQL version you are on?
Is this applicable for you?
http://support.microsoft.com/kb/922527
Satheesh
My Blog |
How to ask questions in technical forum

Jobs in SSIS

Similar Messages

Maybe you are looking for