We're in the process of moving to Commvault, and if i read the documentation correctly, it defaults to a full backup after 24 log backups. There is a registry...

try this

case when sum(dbo.INV_REC_JAN_JUNE_2010.RCP_QTY) is null then 0

else SUM(dbo.INV_SHP_JAN_JUNE_2010.SHIP_QTY) end as rcpt_qty,

case when SUM(dbo.INV_SHP_JAN_JUNE_2010.SHIP_QTY) is null then 0

else SUM(dbo.INV_SHP_JAN_JUNE_2010.SHIP_QTY) end as ship_qty,

When you're performing the detach/attach, might try scripting the action to new query window and see if somethings setting it there.

This has been fixed.

I upgraded to SQL 2008 SP2 and that updated the file associations to 2008.

i ran across an issue like this a few weeks ago. if you're doing these imports via ssis, you can add a script task before the import, i found...

What's the login error message from the SQL Server Log?

Figured out that this is happening after the nodes change in the cluster. Not sure why that's causing it yet though.

This job decided to run again last night, we still haven't figured out how it is starting. Thanks for your ideas.

i think that is a windows property. if you go to display properties, appearance tab, click advanced, and scroll down in the item list to tooltip you should be...

set the date column to not null, then it will use the default if you don't supply any data for that column

One way would be to set up a backup/restore process.

If the job is kicked off from another job, the history says it was invoked by our SQL Agent account, not the job schedule.

I'd wondered if someone had accidentally ran it or it was kicked off by another job or something, but the history specifically says it was invoked by that schedule.

I believe you put the execute sql tasks in a sequence container and set the TransactionOption property of the container to required.