RE: Date Format not working
Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance
Date: Mon, 24 May 2004 13:54:14 GMT
Compare the OS date format for the user who runs the package from
Enterprise Manager and the NT account that SQL Server Agent runs under.
More than likely they are different. When run as a job the package uses the
settings of the SQL Server Agent startup account.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Relevant Pages
- Re: Error running DTS package on a schedule (only!)
... Also, if you are using ODBC, create System DSN, and delete User DSN. ... > | When I try to schedule a job for this DTS package under SQL Server Agent ... > security connection is made using the account you used to start SQL Agent ...
(microsoft.public.sqlserver.dts) - Re: NEWBIE - cant run SSIS package in SQL server agent scheduled job?
... The package will run if I log into the server under the given account and right click on the job and chose "run". ... I added a "step" to the job that ran an operating system command to map the necessary drive prior to running the main package and it worked. ... The connection uses a SYSTEM DSN connection to get data from another source on another machine. ... the SQL Server Agent service is also set up to run under account "x". ...
(microsoft.public.sqlserver.dts) - RE: SSIS Problem
... If SQL Agent is running under Local Account ... When I execute the package in the Execute Package ... when I run this package under the SQL Server agent (the step ...
(microsoft.public.sqlserver.tools) - Re: Error running DTS package on a schedule (only!)
... |I created a DTS package & CAN run it from Enterprise Manager ... | When I try to schedule a job for this DTS package under SQL Server Agent ... the credentials of the currently logged-in Windows NT account ...
(microsoft.public.sqlserver.dts) - Re: SQL Server Cluster Service Accounts
... To change the account under which the SQL Server virtual server or SQL Server Agent runs, you must use SQL Server Enterprise Manager. ...
(microsoft.public.sqlserver.clustering) |
|
