SSIS Error In SQL Agent Job Not Very Descriptive
Mar 14, 2008
Hi there,
I hope I'm posting this in the right section but I have a few SSIS packages that run as SQL Agent jobs that bomb out and does not give me much of a description as why it did. I only get a message that the package failed.
On a different machine, a sql cluster more specific, the job history use to be more elaborate and told me exactly which component errored out.
Is there a setting that I must set somewhere to get a more descriptive error message in the job history?
Thanks in advance
Mike
View 10 Replies
ADVERTISEMENT
Apr 28, 2008
hi all,
I am developing an application in C# which creates SSIS package programatically.These packages perform various activities like transfering data from one server to another,extract data from table,transfering data from sql to msaccess etc.Here I am using the following code to get the description of the SSIS errorcode.
Code Snippet
Public static String GetErrMesg(IDTSComponentMetaData90 MD,Exception Err)
{
try
{
COMException comEx=Err as COMException;
return MD.GetErrorDescription(comEx.ErrorCode);
}
Catch
{
return Err.Message;
}
For example if the error code is 0xC0204018,the application shows its equivalent description as
"The "%1!s!" has a precision that is not valid. The precision must be between %2!ld! and %3!ld! "
But the actual error message is "The Output column "fund" has a precision that is not valid. The precision must be between 1 and 18"
My question is how to show more descriptive error message..like how to replace "%1!s!" to the actual field.
Please give ur suggestions...
View 1 Replies
View Related
Aug 17, 2007
Hi,
Currently I have an event handler on my package that executes a script task on the "OnError" event (at the package level).
One of the error handler's script task's job is to capture the "System::ErrorDescription" and store it to a user variable which is then later sent in an email. That part works fine.
But what I am wondering is, there a way to make the error description more descriptive?? I would like to send a custom error message from one of the tasks in my package, if possible. The task is a script task.
Currently, the "System::ErrorDescription" is just:
The Script returned a failure result.
Which isn't too terribly descriptive! But this is the default error description.
Is there something I can do to change the default error message for my script task?? Is there a way I can set the "System::ErrorDescription" on this script task, perhaps? Or is there another way?
Thanks much
View 3 Replies
View Related
Sep 18, 2007
The following error occurred but did not provide any additional info.
[DTS.Pipeline] Error: The PrimeOutput method on component "Pgrs - tr_hist" (14596) returned error code 0xC02090F5. 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.
For this package I am trying to use DataDirect's ODBC driver for a Progress OpenEdge Database version 9.1E to move data to SQL Server 2005 in order to make use of SQL's BI suite. I have consulted the DataDirect and have that the driver is functioning properly. The driver works perfectly from another application. They suggest that the problem is in the the datareader's or the connection manager's implementation of the driver.
Please tell me what is the cause of this or at least how to troubleshoot this problem.
View 18 Replies
View Related
May 28, 2008
I'm having a hard time locating a listing of potential error codes and the meanings for the Execute Process Task component...can someone assist?
Thanks
View 1 Replies
View Related
May 29, 2008
I'm attempting to run a ssis package via sql server agent.
The package and the DB are on a cluster.
The package runs fine when 'Sql Server Agent' is the run-as.
When I try and use a proxy to run the package, it fails with this error:
Date 5/28/2008 6:21:54 PM
Log SQL Agent (Current - 5/28/2008 6:21:00 PM)
Message
[136] Job CorpFoo New reported: The process could not be created for step 1 of job 0xDAE2A53F27943D4CA412A0D177CAA546 (reason: A required privilege is not held by the client)
I've:
Create Credential to be used by proxy
Create Proxy
Give Permissions to Proxy in SQL Server
Give Permissions to Proxy at the Server for SQL Agent Batch Run
Give Permissions to Proxy at the Server to Connect to SSIS
EXEC dbo.sp_grant_login_to_proxy
@login_name = N'Myapplication_DBO',
@proxy_name = N'Myapplication_Batch_PROXY' ;
EXEC dbo.sp_grant_proxy_to_subsystem
@proxy_name = 'Myapplication_Batch_PROXY',
@subsystem_id = 11;
I've tried a number of things, including adding the sql user (who has access to the proxy) as sys admin on SQL and the OS. That didn't help either.
Has anyone experienced this error? Is there any way to further diagnose this (completely unhelpful) error message?
Thanks,
Steve.
View 2 Replies
View Related
Aug 3, 2006
I am trying to
copy a database from our company's external SQL
Server(production) to our local SQL
Server(development). The Copy Database wizard fails on the step
"Execute SQL Server Agent Job".
Following is the error in the log file.. Please advise
InnerException-->An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
View 7 Replies
View Related
Aug 17, 2006
I have an SSIS package that runs fine through command pormpt although when I try to run it from a SQL Servr Agent Job CmdExec step it bombs out. Please help this has me stumped...the SSIS package uses an XML connection string so certain key settings such as connection strings and email info can be changed easily. Currently this is all on the same machine. I have not moved it beyond where I am developing.
On the command line I am using the following command...
dtexec /F "S:connectionscontacts.dtsConfig" /DE "password"
Below is the output log...
Microsoft (R) SQL Server Execute Package Utility
Version 9.00.1399.06 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 6:59:40 PM
Progress: 2006-08-16 18:59:41.29
Source: Data Flow Task
Validating: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.29
Source: Data Flow Task
Validating: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.71
Source: Data Flow Task
Validating: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.73
Source: Data Flow Task
Validating: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.77
Source: Data Flow Task
Validating: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.77
Source: Data Flow Task
Validating: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.77
Source: Data Flow Task
Validating: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.77
Source: Data Flow Task
Validating: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.79
Source: Data Flow Task
Prepare for Execute: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.79
Source: Data Flow Task
Prepare for Execute: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.79
Source: Data Flow Task
Prepare for Execute: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.79
Source: Data Flow Task
Prepare for Execute: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.81
Source: Data Flow Task
Pre-Execute: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.84
Source: Data Flow Task
Pre-Execute: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.90
Source: Data Flow Task
Pre-Execute: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.90
Source: Data Flow Task
Pre-Execute: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Post Execute: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Post Execute: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Post Execute: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Post Execute: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Cleanup: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.93
Source: Data Flow Task
Cleanup: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.93
Source: Data Flow Task
Cleanup: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.93
Source: Data Flow Task
Cleanup: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.95
Source: Send Mail Task
The SendMail task is initiated.: 0% complete
End Progress
Progress: 2006-08-16 18:59:42.09
Source: Send Mail Task
The SendMail task is completed.: 100% complete
End Progress
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 6:59:40 PM
Finished: 6:59:42 PM
Elapsed: 1.984 seconds
When I try to use the same command within SQL Server Agent Job using a CmdExec step I get the following error...
Description: The package is attempting to configure from the XML file "S:connectionscontacts.dtsConfig". End Info Warning: 2006-08-16 18:40:03.15 Code: 0x80012012 Source: contactsPackage Description: The configuration file name "S:connectionscontacts.dtsConfig" is not valid. Check the configuration file name. End Warning Warning: 2006-08-16 18:40:03.15 Code: 0x80012059 Source: contactsPackage Description: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed. End Warning Info: 2006-08-16 18:40:03.20 ... Process Exit Code 1. The step failed.
Thanks in advance for any help!!!
View 2 Replies
View Related
Mar 11, 2004
Hiya Peeps,
Got a basic update table:
CREATE PROCEDURE CraigSource2Dest AS
INSERT INTO TCraigDest(
MyCertN
,MyResult
,MySpec)
SELECT
TOP 10 dbo.TCertResults.ICertResultsN
,dbo.TCertResults.ICertValue
,dbo.fx_source2dest(dbo.TCertResults.ICertValue)
FROM dbo.TCertResults
GO
As you can see theres a function in the middle of select statement, that returns a value based on what passed into it. The procedure above works fine.
The problem I have is this, can I use the value that the function returns later in the SELECT statement. As an example lets say the table had 4 columns and in the fourth column I wanted to insert the value that the function returned + the word 'TEST'.
I've tried 2 methods of doing this the first :
CREATE PROCEDURE CraigSource2Dest AS
INSERT INTO TCraigDest
(
MyCertN,
MyResult,
MySpec,
MyDerivedColumn
)
SELECT TOP 10 dbo.TCertResults.ICertResultsN
,dbo.TCertResults.ICertValue
,dbo.fx_source2dest(dbo.TCertResults.ICertValue) AS MyNewValue
,MyNewValue + 'TEST'
FROM dbo.TCertResults
GO
When I try this I get the error that MyNewValue is not a valid column name.
And the 2nd method was to try to assign the value returned from the function to a variable. Something like this
CREATE PROCEDURE CraigSource2Dest AS
DECLARE @MyNewValue AS VARCHAR(65)
INSERT INTO TCraigDest
(
MyCertN
,MyResult
,MySpec
,MyDerivedColumn)
SELECT TOP 10 dbo.TCertResults.ICertResultsN
,dbo.TCertResults.ICertValue
,@MyNewValue = dbo.fx_source2dest(dbo.TCertResults.ICertValue)
,@MyNewValue + 'TEST'
FROM dbo.TCertResults
GO
This way gives me ERROR 141 : A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations.
Bit stumped really up to the point that I don't even know what to search for to look for help.
Any help would be grand.
View 2 Replies
View Related
Oct 29, 2007
I have an SSIS package (TransAgentMaster) that I recently modified to include a call to a child package via the file system. The child package creates a text file. When I run the package in dev studio then the child package/text file is produced.
I then imported the TransAgentMaster as a stored packagesfilesystem package into SQL SSIS and executed the package. The child package produced the text file.
I then ran the SQL Server Agent to see if the child package would work and it did not generate the text file. Thus after updating a SSIS package importing the package into SSIS the job that calls the package will not call the child package. Please not that the TransAgentMaster package calls 7 children packages €¦ just not my new one.
Any thoughts why the agent will not run the child newly crated childe package?
View 3 Replies
View Related
Jan 4, 2007
Phil writes "Hi,
Here is my dilemma. I would like to create an SSIS package that will dynamically run different scripts/reports for my company. I would like to use one SSIS package and then dynamically create the jobs based on the schedule of when these scripts should run. For instance, if I have two scripts that create excel documents that run at 2:00 P.M daily I would like to use the job agent and have both of these scripts start at 2:00 PM. Instead of having one run and then the other has to wait until it's complete. First of all, is this even possible? Second has anybody ever played around with this and if so can you give me some guidance?
Thanks,
Phil"
View 2 Replies
View Related
May 22, 2002
I get this error in my Agent after starten to synchronise.
I see the access mdb been created and then deleted and renamed to
name_old.mdb
Do you have some help?
Richard
View 1 Replies
View Related
Jan 29, 2008
I have a really odd one here. We have a production server which is running SQL 2000 Enterprise Edition SP3. It has a number of databases which are backed up nightly. Last night all of the back-up jobs failed with the following error: -
Msg 913, Sev 16: Could not find database ID ##. Database may not be activated yet or may be in transition. [SQLSTATE 42000]
The databases are in good shape - no issues to report. When I run the Agent Job code within a Query Analyser session it works fine.
When I try and re-start the back-up from the Agent Job it continues to fail with the same error.
Any ideas?
View 2 Replies
View Related
Mar 31, 2008
Hello all,
I have designed a SSIS Package. The process of SSIS package is import the data from Excel sheet daily. The package is working fine. When I run from SQL agent job, it is continuously failing. I have created credentials, proxy and I have mapped it. I am doing this process by remote desktop connection. I red lot of articles, nothing was helped me. I hope I will get a solution over here!!
Thanks
Krishna
View 20 Replies
View Related
May 5, 2006
Hi,
Can we allow SSIS to be scheduled via SQL Agent. Is there any security concerns.
Thanks & Regards
Shri.DBA
View 4 Replies
View Related
Oct 27, 2007
Is there a detailed, step by step manual that explains how to set this up?
I can run the package from SSIS but the process to set this up from the job agent is really murky mostly from a security standpoint of setting up user/proxy etc
So I need a cookbook with nice clear explanations
Does one exist?
Thanks
JPS
View 1 Replies
View Related
Aug 29, 2007
I've seen many postings on various forums on how to get SQL agent to execute an SSIS package. I have one that was originally created via the import wizard in SSMS, later modified in VS2005, and then re-imported in SSMS using the Object Explorer interface to load the dtsx file into SQL storage. I've tried several package protection options when importing the package: "Don't save sensitive data" (the package has no passwords in it), server storage and roles, and a specified package password (which I entered as a /DECRYPT command line parameter in the Agent job step). Agent is running using a domain admin account. No matter what I've tried, I still get an error during job execution that it failed to decrypt the password XML node. The package runs just fine when executed manually in the SSIS Object Explorer.
How can I resolve this?
View 6 Replies
View Related
Feb 22, 2008
We are just migrating to sql servr 2005. I have created ssis pkg that runs fine when run mnaulli under BI. However, when I setup the ssis pkg to run as a SQL job. It errors out. Err is listed below. Seems like it is running the job under the SQL Agent account which does not have permissions to access the server i am pulling data from. Can u assit.
1984-2005. All rights reserved. Started: 1:30:51 PM Progress: 2008-02-22 13:30:57.55 Source: DTSTask_DTSDataPumpTask_1 Validating: 0% complete End Progress Error: 2008-02-22 13:30:58.33 Code: 0xC0202009 Source: Laser- Connection manager "FTWSQL" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80040E4D Description: "Login failed for user 'CFC 0SQLA'.". End Error Error: 2008-02-22 13:30:58.33 Code: 0xC020801C Source: DTSTask_DTSDataPumpTask_1 OLE DB Source [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "FTWSQL" failed with error code 0xC0202009. There m... The package execution fa... The step failed.
View 4 Replies
View Related
Feb 25, 2006
I need to pass a value to a package level variable in an SSIS package from a SQL Agent job. If I use dtexecui the syntax for passing the variable in the Property Path is
Package.Variables[User::MyVar].Properties[Value]
and the package runs fine.
When I use this syntax, or any similar format I can think of, in SQL Agent, my job fails. In SQL Agent you put this in the Property Path on the Set Values tab of the Step that runs the package. If I remove passing in the variable my package runs fine.
BOL says use the format Package<container name>.<property name> but I can find no examples. Can anyone provide a working sample to make this work?
Thanks.
View 4 Replies
View Related
Jun 18, 2008
Hello,
I'm new here and hope you will be able to help me.
I have created several SSIS packages with Visual Studio 2005.
They all work fine in debug mode.
I have been able to make them work with a ODBC connection by using a ADO.NET connection.
Then I exported them to the file system in my SQL Server 2005 database and created a task in SQLAgent to run them.
All the packages using the ODBC connection fail with the following error :
Login failed for user XXX
Error : 18456; Severity : 14 , State : 8
This error is a password mismatch.
I tried several database users and checked the passwords multiple times.
It looks like SQL Agent is not able to retrieve the password although it is stocked in both the ODBC connection and the SSIS connection.
Can you help me?
Thanks,
Ares
View 19 Replies
View Related
Jul 19, 2007
Hi,
i have a problem when i schedule an agent on the sql server and i log off the sql server ,
the agent failed with this msg' in the event viewr :
Login failed for user 'sa'. [CLIENT: <local machine>].
the account that run the SQL AGENT is NT AUTHORITYNETWORKSERVICE.
i guess the problem is there but i can't find how to resolve it?
i'll be happy for any help.
10X.
View 1 Replies
View Related
Mar 12, 2008
Hi,
I created a SSIS Package and now i want to run this package from SQL Agent Job. I set up the job and when i run it, it failed
Job Properties:
Type: SQL Server Integration Services Package
Run As: SQL Agnet Service Account
Package Source: File System
Package: \pc17917c$Documents and Settingskdesai1DesktopSSISTest1Test1Package.dtsx
Error i got when i execute the job.
Description: Fauiled to decrypt protected XML node "PassWord" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2008-03-12 10:50:54.48 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2008-03-12 10:50:55.07 Code: 0xC0048006 Source: Drop Table ActiveX Script Task ... The package execution fa... The step failed.
I'm new to the SQL 2005 SSIS. Can you please help resolve this problem?
Thanks,
KD
View 13 Replies
View Related
Apr 10, 2007
Dear All,
I'm using SSIS package to extract text file, and load into SQL Server. I test the SSIS package import manually, it works. Then I'm using SQL Server Agent to set up schedule. According to the log, the job agent work at the scheduled time, yet job agent throw out the error message.
Message1:
The job failed. The Job was invoked by User sysAdmin. The last step to run was step 1 (Extract Data).
Message2:
Executed as user: SQLSERVERsysAdmin. The package could not be loaded. The step failed.
Now I only have 1 step and set up "on success action" then "quite the reporting success". Any clue? Thanks
will
View 11 Replies
View Related
Sep 27, 2006
Okay, I see that dozens of posters have this problem, but none of the threads has a solution: Why does an SSIS package run perfectly fine in VS and in Integration Services, but fail with no details in SQL Agent? Is there another way to have an SSIS package run regularly?
Thanks.
View 5 Replies
View Related
Jan 29, 2007
I have been using SSIS for about two months now and one of the main difficulties I have had is migrating Sql Agent SSIS jobs around environments.
Usually, the SSIS fails because of permissions to file systems, data bases, etc, but until now, I have had to discover these almost by guessing because the job history never game me any useful information. Also, from what I see, the SSIS logs have been unreliable, at best.
What I have done lately is creating Operating System (CmdExec) Steps as part of the job (not SSIS steps) and inserting the output of dtexec.exe into the history.
This seems to give me information that has been really hard to get, otherwise.
My question is (I am no DBA or ETL expert), is this the best way of getting the output of the package when debugging migration issues? Why doesn't the SSIS Steps have a similar feature of outputting useful info to the job history?
View 5 Replies
View Related
Apr 5, 2008
i just completed local testing of an ssis package that I'd like to schedule for execution thru sql agent nightly. I dont mind trying this for a while without deploying either to a database, but am not sure if this is possible. Should my strategy be to get both to a server first or is there a way to plumb them together and see the pkg kicking off nightly before deployment of either?
View 8 Replies
View Related
Jun 20, 2007
Hello! I have an SSIS package that basically collects Excel files from an FTP server, deposits them to a file share on a SQL server and then processes each Excel file into a SQL 2005 database using the ForEach enumerator.
The package runs flawlessly when executed directly on the SQL server. The problem starts when I set this package to run via the SQL Agent. I have looked through these forums and other places and have done what this article suggested http://support.microsoft.com/kb/918760; changing my package protection to
"Dont Save Sensitive" and setup the package to store its configuration in a SQL table. Despite all this I still continue to get this error when the package is run via the Agent:
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "ExcelSourceFile" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
The Excel files are not password protected, no funky settings, nothing complicated, its just a plain Excel file with a few rows of data on one worksheet. The package transfers the files from the FTP server to the share on the SQL server with no problem, I can see that the files exist on the share, so it isnt a case of the Excel connection manager not finding any files to process.
The Agent account is running under administrator privileges and has full access to the share, so it shouldnt be a permissions issue either.
I have no idea what else to check, any ideas?
Thanks!
View 11 Replies
View Related
May 18, 2007
Afternoon all,
This should be brief, hopefully. Every morning all our SSIS updates run on a schedule(s) by SSMS Agent Jobs. Most of the time this is acceptable, however, during the month end accounting process it would be desirable for accounts to be able to run one of the jobs on demand.
Is there a way that this can be done without having to install and use SQL Server Management Studio on account machines? The potential damage that can be done, even inadvertently, with this utility is too great to even consider giving them this package.
Thanks in advance,
Paul
View 1 Replies
View Related
May 1, 2008
Hi,
My package takes 1 global variable and I have set up jobs to run this SSIS with different variable values.
I select the package using the UI provided via the job set up screen. The job step type is Operating system (CmdExec).
When package are run by job, it seems that the job can not find the package. But, how can it not find the package when the package was selected from a list that the UI displayed? The error is below.
"Executed as user: <<LOGGEDIN USER(with admin right)>>. The process could not be created for step 1 of job 0xFECED6C09CC650489084E91C2FCF52FB (reason: The system cannot find the file specified). The step failed."
Thanks a lot in advance.
View 1 Replies
View Related
Feb 6, 2006
I found a similar thread posted under the same title as this by dba123. Unfortunately, his solution does not match my problem.
I have a SSIS package that will run fine in debug mode, will run fine when published to the server when I right click and execute it. However, when I run it through a job, either scheduled or running the job manually, the job fails. There is an entry in the servers application log telling me that "login failed for user xxxxx" where xxxxx is the name of SQL login that I am using. I know that the login works (logged in manually to the server via management studio, and it runs fine when I run it manually). Both connection managers are SQL, no flat files or other data source types. All the commands are T-SQL. The SQL Agent has full database access to both servers that the connection manager connects to - and its NOT the profile that is reporting as failing - it is a domain account.
This is totally bizzare - ANY help would be appreciated.
View 7 Replies
View Related
Mar 17, 2006
Hi everyone,
I have a log table that track my SSIS scheduled jobs. This SQL Agent job runs every 15 minutes for now. The problem is, when I check the status(log) table, I see it fails and succeed at random. I have checked the history and I can't figure out why it is doing this.
Has anyone any idea what is going on? At least for the fact that the package succeeds after it failed shows that nothing is wrong with it. Again when I query my detination table, it is loading data as expected when it runs succeessfully.
Please any idea?
PkgID Pkg_Name Start_Time End_Time Run_Duration Success_Flag
81 Dw_DataImport 35:45.0 37:40.4 0:01:55 Y
82 Dw_DataImport 49:31.0 51:53.5 0:02:22 Y
83 Dw_DataImport 34:26.0 NULL NULL N
84 Dw_DataImport 39:05.0 NULL NULL N
85 Dw_DataImport 45:17.0 48:06.5 0:02:49 Y
Thanks
Omon
View 3 Replies
View Related
Apr 15, 2008
Guys,
Can i schedule a SSIS package by not using SQL AGENT?
Do we have any other options to schedule teh package?
I have worked on other etl tools which have inbuilt options.
please let me know.
Thanks
View 5 Replies
View Related
