Can't create partitions

Hello

WSS 7.8 on 2012 R2.
Remote SQL 2008 R2 SP3 (standard edition)

Logging been working OK for a while since upgrade from 7.6.  Host and application was fresh install of 7.8 but db was upgraded.  Recently disk filled on WSS server, due to files in cache folder.  Turns out the existing database partitions (only 12 of them) are full but the Agent job is not creating a new partition.  If I try and create manually through Triton web interface, no joy.

The actual database is created, the files appear on disk in the correct folder on the SQL server, so NTFS permissions seem OK.  App event log on SQL shows the database created, various properties eg. autoshrink set, the recovery model set to Simple, and then the ETL Agent job runs but errors.  The .mdf and .ldf files are then removed.  The error from the Agent is:

SQL Server Scheduled Job 'Websense_ETL_Job__wslogdb70' (0x05C46BF717285D45B680BAA3550F34DC) - Status: Failed - Invoked on: 2015-01-15 15:22:20 - Message: The job failed. The Job was invoked by Schedule 86 (Websense_ETL_Job__wslogdb70_Schedule). The last step to run was step 1 (step1).

So when I look at the history in Mgmt Studio, I see a more interesting error:

Executed as user: <DOM\SQL_AGENT_ACCOUNT>. usp_new_partition() : 1: Invalid column name 'record_number'. [SQLSTATE 42000] (Error 50000).  The step failed.

I have deleted and recreated the jobs using the provided SP.

There appear to be no other abnormal errors on either the SQL host or the WSS host.  That SQL server is used by a few other applications which are working fine.

I have followed my nose through google searches, looking at various things.  One thing I looked at were the triggers in wslogdb70 and there may possibly be a relevant duplicate but I have nothing to compare against.  In sys.triggers I have 23 rows, the name values or which are

WsUpdateUserDirObjectTrigger
insert_trigger_db_maintenance
insert_trigger_wse_version
wsPartitions_Trigger
wsPartitions_dTrigger
usp_wse_db_event_trigger
trigger_wse_dashboard_config
insert_trigger_wse_etl_db_config
insert_trigger_wse_db_config
insert_trigger_wse_ibt_config
insert_trigger_wse_trend_config
trigger_ua_etl_config
trigger_wse_etl_config
update_trigger_filter_sets
insert_trigger_filter_sets
insert_trigger_filter_set_params
WsExpTriggerRequestCount
insert_trigger_report_spec
update_trigger_report_spec
trigger_wtg_etl_config
insert_trigger_wse_products
trigger_hosted_etl_config
trigger_amt_etl_config

Might be barking up completely the wrong tree!

Anybody seen anything like this before?

The account used to access SQL is a domain account, currently a member of sysadmin as well as a local Administrator of the both machines but given the Agent error about 'invalid column name' I think the problem is not permission related?

Any suggestions?

Thanks

D