IT Answers » SQL Jobs

Schedule SQL job to run and export to CSV file

Sesa — Thu, 23 Feb 2012 23:45:47 +0000

New Answer by Michael Tidmarsh

How do you set a SQL Server job step status?

Redwine — Wed, 12 Jan 2011 23:28:40 +0000

I am running SQL Server 2005. I have a job that has six steps to load a database table from an external source. The external source is required to send the file nightly. In system testing I found this is not always the case. I created a batch ‘step’ (Step 3) to check if the file has been sent (see code below). If the file is present I use today’s file. If the file is not present I use last night’s file (demographic data). I cannot set Step 3 ‘Job Step Properties – Advance tab’ to ‘on failure action’ because logically it will not fail. I want to modify the code to ‘move’ last nights’ file and then indicate the step has failed (force failure – set the job step status property?). Then I would execute the next step (Step 4) that notifies the external source of not receiving the file. I only want to execute Step 4 when I do not receive the file. How do I set the job step status property in Step 3 to indicate ‘failure’ after moving the file? Does anyone have any solutions? STEP 3 code @echo off Retailer file transfer. if exist “E:SQL DatabasesSQL JobsSQL Import DataGPRetailer.del” goto done echo NO RETAILER FILE TO TRANSFER! :begin move “E:SQL DatabasesSQL JobsSQL Import DataGPRetailer.old” “E:SQL DatabasesSQL JobsSQL Import DataGPRetailer.del” echo Moved! :done echo Done!

SQL 2008 job problem

DavidHa!! — Thu, 02 Dec 2010 15:28:33 +0000

I have a schedule SQL2008 job to export the contents of a table to a text file each day. The job runs fine when I manually execute it, but if the schedule executes it, only 4 or 5 lines of text out of about 13000 are produced to the text file. Any ideas anyone? The job script follows: EXEC xp_cmdshell ‘bcp “SELECT * FROM pesticide..krspestdata” queryout “C:tempPestproducts.txt” -T -c -r”^” -t”|”‘

Microsoft SQL Server BCP Utility password

Redwine — Tue, 23 Nov 2010 19:42:31 +0000

I am executing a Microsoft SQL Server Job that runs a BCP Utility. The utility loads a table from a file using the ‘in’ argument, a format file and an error file. I have ‘hard coded’ the user name and password in the command line using the ‘U’ and ‘P’ arguments.

I am looking for a method without using the ‘hard coded’, clear text user name and password.

Has anyone done this using the BCP utility?

SQL Server 2005 Express

Db23 — Mon, 27 Sep 2010 06:29:35 +0000

Hi,

Is it worthwhile to schedule optimisation job (update stats and rebuild index) on another server so it can be run on a database that was created on SQL Server 2005 Express from an application installation?

I know it is probably a good idea to atleast change the autogrowth setting from 1MB but what about the weekly database optimisation jobs?

Thanks.

SQL DTS package scheduling

Gic — Mon, 07 Dec 2009 01:53:10 +0000

When a DTS package is scheduled to run at a specific time of day, is it done through the use of a stored procedure or a job?

My DTS package runs normally, but hangs when run as a SQL Job

Dring57 — Tue, 28 Apr 2009 18:01:47 +0000

Hi, I’m trying to run an Ms Access .mbd file through a MS SQL 2003 Server. The package runs normally and works when I start the job, but simply hangs when I run the package as a a scheduled job. I’ve designed a DTS local package as follows:
‘**********************************************************************
‘ Visual Basic ActiveX Script
‘************************************************************************
I
Function ConvertIssue3()
Dim objDB
Set objDB = CreateObject(“Access.Application”)
objDB.OpenCurrentDatabase(“H:\dep\Convert\Convert.mdb”)
objDB.Run “ConvertIssueSlips”
objDB.CloseCurrentDatabase
objDB.Quit
ConvertIssue3 = DTSTaskExecResult_Success
End Function

Originally I thought it might be a security issue, but when I change ownership of the job to a user without admin privileges, the job simply fails, where if I make sure the owner is an admin, the job hangs. In the package I changed clicked both boxes in the work flow properties tab: Use ActiveX script and Execute on main package thread. I’ve tried just about every combination of these options, and I still have the hang problem.

Does anyone have any idea what might be going wrong. I’ve searched the internet for a while and have yet to come up with a solution. If not, does anyone know of a different way to run the Ms Access file? Any advice will help. Thanks.