Job Fails But Package Will Run From MSDB
Jan 25, 2006
I created a package for importing data from a flat file to an existing table in SQL Server 2005 using Management Studio and the administrator account working directly on the server through a remote login. I saved the package to MSDB.
I can see the package listed when I connect to Integration Services through Management Studio and expand the MSDB folder. In that location I have the option to run the package and it will run successfully. However, I cannot edit the package.
When I try to create a scheduled job using Sql Server Agent, where the first step is to run the package using the administrator login, the execution fails, and the job history will only tell me that the step failed. The Sql Server Agent log shows that the job started and completed. No error is shown. The Administrative Tools Event Viewer Application log shows only that the job started and failed. Security log shows no errors. System log shows no errors.
What am I doing wrong? How can I edit and schedule this package?
View 6 Replies
ADVERTISEMENT
Jun 11, 2007
I did a small package with only one ODBC connection (Merant 3.70 32-Bit Progess). This package runs well in Visual Studio and fails when runs by SQL Server Agent.
Configuration:
SQL Server Agent on a 32Bit server.
The ODBC connection configuration in available on System DSN on this server.
The user of Server Agent have full access (Admin).
Connect Manager Provider: ".Net ProvidersOdbc Data Provider"
SQL Server version: 9.0.3042
Error Message:
Executed as user: TEKCON cadmin. ...ion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 16:50:33 Error: 2007-06-11 16:50:33.62 Code: 0xC0047062 Source: Data Flow Task DataReader Source [1] Description: System.Data.Odbc.OdbcException: ERROR [HYC00] [MERANT][ODBC PROGRESS driver]Optional feature not implemented. ERROR [HY000] [MERANT][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS ERROR [IM006] [MERANT][ODBC PROGRESS driver]Driver's SQLSetConnectAttr failed. ERROR [HYC00] [MERANT][ODBC PROGRESS driver]Optional feature not implemented. ERROR [HY000] [MERANT][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS ERROR [IM006] [MERANT][ODBC PROGRESS driver]Driver's SQLSetConnectAttr failed. at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode) at System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcCon... The package execution fa... The step failed.
I created a .bat file with this instruction and It's run well:
dtexec /f "C:Program FilesMicrosoft SQL Server90DTSPackagesIntegration Services Project estcom.dtsx"
pause
Why it's not running with SQL Server Agent???
View 7 Replies
View Related
Nov 27, 2006
Hi,
I have a intermittent problem with my ssis packages. I have a couple of packages running on a schedule with SQL Server Agent wich sometimes gives me the following errors in agent history:
Message
Executed as user: MyDomainSQLAgentServiceAccount. 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: 21:05:00 Could not load package "MSDBMyPackageName" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 21:05:00 Finished: 21:05:00 Elapsed: 0.047 seconds. Process Exit Code 5. The step failed.
When the package does'nt fails it gives me the following message:
Message
Executed as user: MyDomainSQLAgentServiceAccount. 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: 21:10:00 DTExec: The package execution returned DTSER_SUCCESS (0). Started: 21:10:00 Finished: 21:10:02 Elapsed: 1.312 seconds. Process Exit Code 0. The step succeeded.
The jobs moves data between the sql server that executes the code and a SQL 2000 database on another server. Does anyone recognize this error?
View 1 Replies
View Related
Mar 9, 2007
Hi
I am trying to load a ssis package into a folder (lets say SSIS packages) that I created in MSDB but its geeting saved in the root (MSDB) not into the SSIS packages folder...I am doing this thru C#...
View 3 Replies
View Related
Feb 27, 2006
I have designed a few SSIS packages in the BI Development studio and deployed them to the msdb database of my SQL server using the generated Deployment Utility.
They deployed and executed just fine, but, I would like to better organize them into folders within the msdb storage area.
Is there a way to tell the project or the generated Deployment Utility to deploy the packages to a specific folder within the SSIS Packages / msdb storage area on the SQL server?
Thank you for any help!
-Tim
View 4 Replies
View Related
Jun 30, 2006
I created a package using the ImportExport wizard and saved it to the local Sql server. Under Management Studio I can see the package, can run in, import it, export it BUT how am I supposed to edit (modify the thing) it?
TIA,
barkingdog
View 9 Replies
View Related
Dec 28, 2007
I have a question about where package is stored if you select sqlserver or SSIS package store (msdb). Is both of these going to the same place sysdtspackages90. On one of my systems I was saving as sqlserver but when users created a job they where using SSIS package store msdb. This seems to be working, though I would have thought that they were to different locations. On another system when I did same thing the job failed, and looked like maybe it was running wrong version, but when I resaved project as SSIS package store(msdb) then it did work. Even though I had earlier saved that package under sql server. So on 1 system it looks like they are the same on the other system I am not sure.
So if you can clarify for me what the difference between the two areas are if any?
View 1 Replies
View Related
May 7, 2007
We have just started using SQL 2005 and released our first few projects to prodcution. We are currently using msdb storage for SSIS packages in production using the 'rely on server storage' for protection level and separating each subject areas by folders under msdb in the management studio.
However some of our DBA's feel that this is not the right approach and we should be storing as XML.
Anyone has any recommendation for either or considerations to be taken when deciding what storage to use?
Thanks!
View 1 Replies
View Related
Mar 23, 2006
Which tool is used to maintain packages stored in the MSDB. Do you have to export them as file based to edit them?
View 3 Replies
View Related
Oct 5, 2015
We are upgrading from SQL 2008 R2 to 2014. I have a 2008 SSIS package converted in VS 2013 and deployed to MSDB as package deployment model. It ran ok from an agent job. However, after I converted the same package into project deployment model, converted the connection manager to project model, deployed the project (with the package) to SSISDB and applied environment variable for its configuration, the agent job failed for not able to acquire connection to what used to be the connection manager.Â
Both agent jobs run understand the same account on the server. The account has access to the databases that are connected in the packages. The job/packages has been running ok on 2008 R2 accessing the same db for years.Â
The environment variable for the connection string is defined as "Data Source=ServerABC;Initial Catalog=DB123;Provider=SQLNCLI11;Impersonation Level=Impersonate;"
Why can't the job connect to the database when it runs a package from SSISDB?
View 14 Replies
View Related
May 22, 2008
Hello,
I need to run SSIS packages with the 32 bit dtexec version, and I am storing these files into the MSDB package store, in SQL Server 2005. I have chosen to encrypt sensitive data with password, and then to execute the packages with xp_cmdshell.
The problem is that I receive the following message when I try to run it from management studio (when running this, I am logged in with the sa user): exec master..xp_cmdshell 'dtexec /Ser ServerName /SQL "TestFolderPackage" /De "testPass"'
€œMicrosoft (R) SQL Server Execute Package Utility
Version 9.00.1399.06 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
NULL
Started: 9:41:29 AM
Error: 2008-05-22 09:41:29.70
Code: 0xC0016016
Source:
Description: Failed to decrypt protected XML node "DTSassword" 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€?
If I run the same package with the same command specified above, but without sensitive data in it (a simpler version with no passwords and connection strings, it works fine)
exec master..xp_cmdshell 'dtexec /Ser ServerName /SQL "TestFolderPackage"'
If I run the firs package version (with sensitive data and password protected) from the command line, everything works well:
DTExec.exe /ServerName OLAP /SQL "TestFolderPackage" /De "testPass"
I know in ASP.NET when encrypting web.config section, the system stores the decryption keys in a app data folder, and in order to be able to read from the encrypted web.config, the user under which runs the ASP.NET must be granted access to that folder, by running asp_regiis.exe with some parameters. I believe here a have a similar problem, with users not being granted access to encryption keys.
Thanks in advance
View 2 Replies
View Related
May 16, 2006
There is an execute package task that calls the child package. Both parent and child packages have the same password and the passwork is entered into the execute package task. Both packages reside in the same directory path.
Error: Error 0xC0012050 while loading package file "C:Documents and SettingsuserMy DocumentsVisual Studio 2005ProjectsExecutePackageTestExecutePackageTestExtractandWrite.dtsx". Package failed validation from the ExecutePackage task. The package cannot run.
When ExtractandWrite.dtsx is executed by right-clicking on package, the package executes without any errors.
DelayValidation = True for the Execute Package Task tasks is set and DelayValidation for the connection manager is set to True.
Does anyone have any thoughts as to what might be causing this error?
Thanks in advance for your assistance.
View 1 Replies
View Related
Nov 21, 2005
Whenever I start my SQL Express 2005 database, I get the following in the logs :
View 10 Replies
View Related
Sep 2, 1999
I set up a DTS package to run every night on my SQL 7 Server.
It is supposed to write a text file of modified rows every night.
It was working fine until I changed the password for sa, now it
fails. Also in Enterprise Manager, when I try to look a the package
properties, I get a "login failed for user sa" package error.
What to do?
View 1 Replies
View Related
Mar 2, 2001
I have stored procedure that uses the xp_cmdshell procedure to use the dts run to run some dts packages. This package exports data into an Access 97 database. When I run it I get this error:
Error: -2147467259 (80004005); Provider Error: -533791822 (E02EFBB2)
Error string: Could not update; currently locked by user '(unknown)' on machine ''.
Error source: Microsoft JET Database Engine
Help file:
Help context: 5003218
If I right click on the local package and select execute it runs with no problem. Any ideas what is going on?
View 2 Replies
View Related
Nov 8, 2002
I have a DTS package set up to push data out to several sites. When I execute the package it runs perfectly. When I schedule it as a job it fails.
I checked the proxy account in the SQLAGent properties and there is a check mark there. But the job still fails.
Does anyone have any ideas?
View 8 Replies
View Related
Dec 18, 2000
I'm trying to run a job which moves data from one machine to another. I can manually execute the package successfully, but the job always fails. I get the dreaded error message 18456, "login failis for user "". I have double checked the logins for both machines,(sql server agent AND the sql server authentication).
Also, I can run a select statement (from server_ to server_2) successfully from query analyzer i.e.
Select *
from <linked_server_name>.<database>.<database_owner>.<table_name>
however, if I run this query from server_2 to server_1 I get the failed login message similar to the error message found in the job history. Since both servers accept nt logins, where is my problem? They are both set up as linked servers, and they are both mssql oledb.
Any suggestions will be appreciated!
thanks
View 1 Replies
View Related
Dec 12, 2005
Hai ....,
I have a DTS Package that is used to dispatch mails to all the customers. When I execute the package manually by selecting it and then clicking Execute Package from the context menu, it executes to completion successfully. But when I schedule to execute it using Job, then I get the following error message:
... DTSRun: Executing... DTSRun OnStart: DTSStep_DTSExecuteSQLTask_2 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_2 DTSRun OnStart: DTSStep_DTSActiveScriptTask_1 DTSRun OnFinish: DTSStep_DTSActiveScriptTask_1 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_3 DTSRun OnError: DTSStep_DTSExecuteSQLTask_3, Error = -2147220421 (8004043B) Error string: The task reported failure on execution. Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts80.hlp Help context: 1100 Error Detail Records: Error: -2147220421 (8004043B); Provider Error: 0 (0) Error string: The task reported failure on execution. Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts80.hlp Help context: 1100 Error: -2147467262 (80004002); Provider Error: 0 (0) Error string: No such interface supported Error source: Microsoft OLE DB Provider for SQL Serv... Process Exit Code 1. The step failed.
FYI: This Package is under machine7. When I copy the package to my system (machine3) and execute it using Job, it succeeds :rolleyes:
Please help me out of this problem :confused:
View 5 Replies
View Related
May 19, 2005
SQL Server is running on my PC. The server name is 'ASPEN'. When I create a DTS package to export a local database to our live site, I must use 'LOCAL' for the server name, not 'ASPEN'. Everything runs fine the first time, but later, when I try to execute, or even view, the local package I saved, I get the following error:
[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied.
Can anyone explain this?
View 3 Replies
View Related
Jun 22, 2004
Hi,
I have a DTS package which when I execute it manually, it executes perfectly. I need to schedule it and therefore had to use the scheduler which would creata a job for the package. The problem is that job. It does not execute; it fails every time. The error message is: Sql server does not exist or access is denied.
I have tried to trouble-shoot by setting up an alias for the server in the client network utility for sql server. I also create a new dsn with the new alias. It still failed with the same error message. I edited the properties of the dts package to connect to the server's ip instead of it's alias or logical name. Still fails.
Any ideas anyone?
Maria
View 1 Replies
View Related
Jan 11, 2008
There is a DTS package that fails to run for one user. The DTS runs for other users. The DTS even runs when the user signs onto another Server.
The error message that the user gets is the following:
The number of failing rows exceeds the maximum specified.
TransformCopy 'DTSTransformation_1' conversion error: Conversion invalid for datatypes on column pair 1 (source column 'F1' (DBTYPE_WSTR), destination column 'PostDt'(DBTYPE_DBTIMESTAMP))
As previously stated, if the user signs onto another Server with SQL Server on it, the DTS performs a successful transformation.
Has anyone seen this error. I've been looking over all roles and security and have not been able to find any differences between user setup.
Thanks in advance.
View 7 Replies
View Related
Jan 25, 2008
I have an SSIS package that runs just fine in BI but when I go to run it as a job I get this error message:
SQL Server Scheduled Job Status: Failed - Invoked on: 2008-01-25 12:23:08 - Message: The job failed. The Job was invoked by User. The last step to run was step 1 (Step 1).
I have created a credential with domain admin rights and a proxy that uses the credential. The domain admin account is a member of the SQLServer2005SQLAgentUser group. The package protection level is set to EncryptSensitiveWithKey.
View 9 Replies
View Related
Jul 20, 2005
Hi,A DTS package which is running fine when execute ,always fails asscheduled job.I read from the previous posts about MS KB article 269074, securityand MDAC, but I don't understand and don't know how to solve it.Please help.My scenerio:SERVER : MS Windows 2000 server is in a PRODUCT DOMAINMS SQL SERVER 7.0 SP2- Agent started up by SYSTEM ACCOUNT andConnection as NT AuthenticationWORKSTATION (Enterprise Manager as Tool to connect MS SQL SERVER andwrite and schedule DTS Package): MS Windows XP connect as NT Authenticationbut in WORKGROUP DOMAINBest RegardsNipon Wongtrakul
View 1 Replies
View Related
Dec 31, 2007
Like the name says, I'm trying hard, but I'm obviously missing something. Okay, I'm new to SSIS. I'm trying to write a job that deletes some Excel files on the server, copies some Excel files from a Sharepoint instance to the location where the deleted files were, runs an executable to manipulate those files, and then imports them to my SS instance.
the package runs fine when I run it from Managment Studio after installing it on the server. The 'execute task' fails when I run the job containing the package. After creating a proxy to have the SQL Server agent Service run with appropriate permissions, I thought I would have been rid of permissions issues (I gave the proxy way too much permission in an effort to narrow in on my issue), but I could still be missing something.
The job doesn't get into the package enough to even start writing to my log file, and all I get in the job history is the very cryptic 'DTExec: The package execution returned DTSER_FAILURE (1) ' error. If anyone has ideas, I would greatly appreciate being shown the error of my ways.
Thanks!
View 6 Replies
View Related
Nov 20, 2006
I have a large number of SSIS packages, which I have developed over the last few months.
Having written and tested them locally, running in VS05 etc - I have moved them to a server, stored in the MSDB database.
I am having real troubles with packages that move tables from one database to another.
I am working on a migration project, so I have several packages that move tables from the source database, into my staging database.
One package which will not run at all, basically just moves 15 tables from database A on my server to database B.
The package is essentially a few SQL tasks to create tables, then a data flow.
The data flow contains the table movements as an OLE DB source to an OLE DB destination. No intermediate processing.
In an attempt to get some meaningful logs of the reasons for failre I ran the package from the commandline with the output piped to a text file. That text file contained the following error:
Error: 2006-11-20 11:48:47.78
Code: 0xC0202009
Source: Data Flow Task Source - tblParking [1641]
Description: An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Protocol error in TDS stream".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Shared Memory Provider: No process is on the other end of the pipe.
".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Shared Memory Provider: No process is on the other end of the pipe.
".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Shared Memory Provider: No process is on the other end of the pipe.
".
End Error
Error: 2006-11-20 11:48:47.78
Code: 0xC0047038
Source: Data Flow Task DTS.Pipeline
Description: The PrimeOutput method on component "Source - tblParking" (1641) returned error code 0xC0202009. 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.
End Error
Error: 2006-11-20 11:48:47.84
Code: 0xC0047021
Source: Data Flow Task DTS.Pipeline
Description: Thread "SourceThread1" has exited with error code 0xC0047038.
End Error
I've googled for most of the error messages there, and tried applying some of the things I found.
I've set the commit size on the OLE DB destination to 10k rows.
I've set the number of engine threads to 2.
The SQL Agent service is started by a domain user that has sufficient server and database roles to do what it needs - other packages run fine.
I'm really stumped here now - this package will run perfectly in visual studio, but fails when ran
as a scheduled task, and I'd really appreciate any advice or pointers
View 6 Replies
View Related
Jan 16, 2007
Two scenarios, 1 worked, 1 didn't:
First package I execute SQL (select top 10 * from MyTable) in my SQLServer2005 database.
I scheduled it and it ran sucessfully.
I changed the execute SQL to run against an external Oracle database. (Select * from SomeOracleTable where rownum <= 10). I preview to make sure the query works and it does return a result set. I execute the package in the Visual Studios IDE and it works. I save with encryptAllWithPassword to the SQL server. I go into the scheduler and select the package from SQL Server (as opposed to the file system). I set the step to execute the package off the server. I enter the security key by clicking on the configuration tab. I assume it saves the password to the package. I click OK, and schedule it for one time execution.
It fails.
I have looked at:
http://support.microsoft.com/default.aspx/kb/918760
but nothing jumps out at me that i did anything wrong. I mean I did Resolution Method #2, and #3 and it still fails.
Can someone please help???
Ryan
View 11 Replies
View Related
Jun 19, 2007
Background:
I have a package that reads data from an SAP table and populates a SQL table.
The package was developed using a custom source component I created to connect to SAP. The package runs with no errors in the Business Intelligence Development Studio.
I deployed the package to my test SSIS server successfully using a package password.
The Run Package option runs the package with no errors.
Problem:
I created a Job under the SQL Server Agent and configured a single Step to execute my package. This fails with the following error:
Code: 0xC0047062
Description: System.InvalidCastException: Unable to cast object of type ...
Description: component "SAP DB Source" (281) failed validation
The cast is fine as far as I can tell, so I'm not sure why this error occurs. I found other reports of this strange error message, but no solution. Any help is greatly appreciated!
Philip
View 1 Replies
View Related
Mar 10, 1999
I have a Local DTS Package which will execute fine...no problems. When I try to schedule it from my NT 4.0 Workstation to the NT 4.0 Server, I get the job scheduling dialog box...fill it out...click OK...and NOTHING.
No error message, nothing in the SQL error log, nothing in the NT logs, no job in the schedule! When I perform the same task at the server logged in as Administrator it schedules successfully.
Any feedback would be greatly appreciated.
Eric
View 2 Replies
View Related
Jan 25, 2007
I am trying to configure emails alerts on DTS package on one of my servers , i am getting an error somthing like i need to add a new profile.I received emails every day from the scheduled jobs which succeed every day
View 3 Replies
View Related
Jun 7, 2004
I have a SQL DTS package that imports a text file as one wide column into a two column SQL table, one is an identity seed. So essentially I import then parse the data using the index key as it is 3 seperate lines of data. All works fine by running the DTS package using execute. When I schedule this as a job it fails. It indicates that I have additional white space after a column. Any thoughts on why this can ocurr?
View 4 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
Jul 5, 2006
Hi,
I have a SSIS package that I developed using Business Intelligence Development Studio. I imported it into our SQL Server database and it runs fine (when I connect to Integration Services within SQL Server Management Studio, and run the package). But when I created a SQL Server Agent job comprising 1 step, to run this package, it fails. The failing step attempts to read data from a MS Access 2000 DB into SQL Server 2005.
I added logging to the package, and got the following error logged to the Event Viewer:
"The AcquireConnection method call to the connection manager "CurrentYearPCStats" failed with error code 0xC0202009."
I then created a new Operating System (CmdExec) step, calling DTEXEC with the command line copied from that generated by the SSIS step. The command line is:
"C:Program FilesMicrosoft SQL Server90DTSBinnDTEXEC.EXE" /SQL "AFAReductionAFA Reduction Integration" /SERVER <ourservername> /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
This failed with the same error in the Event Viewer, but for some reason also produced a meaningful error in the SQL Server Agent job's View History:
Description: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "The Microsoft Jet database engine cannot open the file '\<anotherservername>PCStatsliveCurrData.mdb'. It is already opened exclusively by another user, or you need permission to view its data."
Please note that the SQL Server Agent runs using user id sqlservice, by default, and I have amended this user's Windows account to make it a Domain Admin.
Please let me know why I might get this error, when the package runs OK on its own.
Many thanks,
Keith.
View 6 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
