Got this when I ran my sp__updatestats procedure in a SQL Agent jobstep, but it worked in Query Analyzer. The reason? The default settings are probably different in QA rather than external connections similar to SQL Agent.

Msg 1934, Sev 16: UPDATE STATISTICS failed because the following SET options have incorrect settings: 'ARITHABORT'. [SQLSTATE 42000]

The solution was to recreate the procedure that ran UPDATE STATISTICS using a SET command within the procedure. 

CREATE PROCEDURE dbo.sp__UpdateStats
AS
SET ARITHABORT ON 
SET QUOTED_IDENTIFIER ON 
...

We started to get this problem after I added a computed column to a table. 

Searching for Wildcard Characters

You can search for wildcard characters. There are two methods for specifying a character that would ordinarily be a wildcard:

Use the ESCAPE keyword to define an escape character. When the escape character is placed in front of the wildcard in the pattern, the wildcard is interpreted as a character. For example, to search for the string 5% anywhere in a string, use:


WHERE ColumnA LIKE '%5/%%' ESCAPE '/'
In this LIKE clause, the leading and ending percent signs (%) are interpreted as wildcards, and the percent sign preceded by a slash (/) is interpreted as the % character.

Use square brackets ([ ]) to enclose the wildcard by itself. To search for a hyphen (-), instead of using it to specify a search range, use the hyphen as the first character inside a set of brackets:


WHERE ColumnA LIKE '9[-]5'
The following table shows the use of wildcards enclosed in square brackets.

Symbol Meaning
LIKE '5[%]'
5%

LIKE '5%'
5 followed by any string of 0 or more characters

LIKE '[_]n'
_n

LIKE '_n'
an, in, on (and so on)

LIKE '[a-cdf]'
a, b, c, d, or f

LIKE '[-acdf]'
-, a, c, d, or f

LIKE '[ [ ]'
[

LIKE ']'
]


When string comparisons are performed with LIKE, all characters in the pattern string are significant, including every leading and trailing blank (space). If a comparison to return all rows with a string LIKE 'abc ' (abc followed by a single space) is requested, a row in which the value of that column is abc (abc without a space) is not returned. The reverse, however, is not true. Trailing blanks in the expression to which the pattern is matched are ignored. If a comparison to return all rows with a string LIKE 'abc' (abc without a space) is requested, all rows that start with abc and have zero or more trailing blanks are returned.

Automatically add a schedule to a SQL Agent job. This example adds one that will run two hours from now, once. Left to do: what if no longer today?

More tokens.

DECLARE @vcSchedule VARCHAR(128),
   @nJOBID uniqueidentifier,
   @nDATE INT,
   @nTIME INT,
   @nHours INT
SELECT @vcSchedule = 'Reschedule',
   @nJOBID = CONVERT(uniqueidentifier, [JOBID]),
   @nDATE = [DATE],
   @nTIME = [TIME],
   @nHours = '020000' + @nTIME
--SELECT @nJOBID, @nDATE, @nTIME, @nHours 

IF EXISTS (SELECT [name] FROM [msdb].[dbo].[sysjobschedules] WHERE job_id = @nJOBID AND name= @vcSchedule)
  EXEC msdb..sp_delete_jobschedule @job_id=@nJOBID, @name=@vcSchedule

EXECUTE msdb.dbo.sp_add_jobschedule 
   @job_id = @nJOBID, 
   @name = @vcSchedule, @enabled = 1, 
   @freq_type = 1, 
   @active_start_date = @nDATE, 
   @active_start_time = @nHours, 
   @freq_interval = 1, --once
   @freq_subday_type = 1, --At the specified time
   @freq_subday_interval = 1, 
   @freq_relative_interval = 0, 
   @freq_recurrence_factor = 0, 
   @active_end_date = 99991231, 
   @active_end_time = 235959

A few interesting things to note about this graphic.

1. The query is an INSERT into myVIEW
2. It is using tempdb to process the INSERT. I think it is because I had to add a SELECT * FROM inserted trigger to even get INSERTs to work. In addition I had to add a WHERE clause matching the partioned tables CHECK constraint and explicitly insert to the appropriate table.
3. I thought tempdb needed to have the data files all the same size to be utilized. So here we can see the files which are the same size are used, the bigger one is not.

ps. This is a test. The files will be the same size after the server is restarted.

Run trace for one database at a time. 

The events and data columns used by the Index Tuning Wizard are 
    SQL:BatchCompleted and the
    RPC:Completed events in the TSQL category, and the
    EventClass and Text data columns.

Save as trace file or table. NOTE: ITW won't run on a read-only database.

INSERT INTO OPENROWSET('Microsoft.Jet.OLEDB.4.0',
'Excel 8.0;Database=E:\MSSQL\Reports\JobSchedules.xls;',
'SELECT JobName, ScheduleName, next_run_date FROM [Sheet1$]')

select j.name JobName, s.name ScheduleName,
 next_run_date
from msdb..sysjobs j
join msdb..sysjobschedules s
 on j.job_id = s.job_id
where j.enabled = 1
 and s.enabled = 1
ORDER BY
 j.name
GO

-- Note:
--  Requires E:\MSSQL\Reports\JobSchedules.xls to already exist with the correct columns.