Hi Mike,

>I can't even begin to guess what might be filling up the transaction log for such a small update. Try using the Profiler (or Trace in 6.5) to get a picture of what's being sent to the server.

It's really odd. All of the fields except the memo fields seem to get written with an "Insert" command. Then the log is filled with lines like this:

-- 27/1/00 09:41:23.153 SQL (ID=28, SPID=21, User=she2000(LEXWARE\PAULINE), App='', Host='PAULINE'(ffc5325d) )
Pad out the uK waste.brok_addr 0x361400000000000001000000249B0300 WITH LOG
go
-- 27/1/00 09:41:23.216 Duration 0.063, CPU 0.000, Reads 0, Writes 0
 
-- 27/1/00 09:41:23.216 SQL (ID=28, SPID=21, User=she2000(LEXWARE\PAULINE), App='', Host='PAULINE'(ffc5325d) )
 start of theLK waste.brok_addr 0x361400000000000001000000249B0300 NULL 0 WITH LOG
go
-- 27/1/00 09:41:23.216 Duration 0.000, CPU 0.000, Reads 0, Writes 0
 
-- 27/1/00 09:41:23.233 SQL (ID=28, SPID=21, User=she2000(LEXWARE\PAULINE), App='', Host='PAULINE'(ffc5325d) )

	Take the cuLK waste.brok_addr 0x361400000000000001000000249B0300 NULL 0 WITH LOG
go
-- 27/1/00 09:41:23.233 Duration 0.000, CPU 0.000, Reads 0, Writes 0
 
-- 27/1/00 09:41:23.233 SQL (ID=28, SPID=21, User=she2000(LEXWARE\PAULINE), App='', Host='PAULINE'(ffc5325d) )
temp3
	StoreLK waste.brok_addr 0x361400000000000001000000249B0300 NULL 0 WITH LOG
go

and various other references to the memo field waste.brok_addr. This goes on until the log file is full.

We're thinking of turning off the log alltogether for our database, at least as a temporary solution.

Best.

Matt.