Hi,

I asked this question on the Visual FoxPro forum, and got some help from Michael Levy. However, I thought I'd post it here to see if anyone else can help.

We have a Visual FoxPro application updating a database on SQL Server 6.5. The problem we have is that adding data to a text field [a memo field in Visual FoxPro] appears to be causing the transaction log to fill up. We tested, starting with an empty 10 Mb transaction log, with the result that the log became completely full when we attempted to update a single record. The update failed when the log was full.

The following is part of the log file. The field waste.brok_addr is the text/memo field in question.

-- 27/1/00 09:41:23.090 SQL (ID=28, SPID=21, User=she2000(LEXWARE\PAULINE), App='', Host='PAULINE'(ffc5325d) )
INSERT INTO waste (idwaste,environment_id,reference,descrip,container,quantity,hold_name,hold_addr1,hold_addr2,hold_addr3,hold_pcode,pwaste,iwaste,cwaste,dwaste,lwaste,lnumb,lnumb_issue,rwaste,rnumb,rnumb_issue,elwaste,elreason,erwaste,erreason,col_name,col_addr1,col_addr2,col_addr3,col_postcode,col_auth,disp_auth,exporter,lic_hold,lic_numb,lic_iss_by,lic_exempt,lic_exe_reason,reg_carr,reg_numb,reg_numb_iss,reg_exempt,reg_exe_reason,trans_addr1,trans_addr2,trans_addr3,trans_pcode,trans_date,trans_time,brok_name,brok_addr,signed1,signed2,trans_name1,trans_name2,represent1,represent2,reassess,revision_no,user_,createdate,amenddate,site_code) VALUES (8,0,'7                   ','dsfgsdgsd                                         ','dgsdg                         ','33333                         ','dsfgdsgfsdgsd                                     ','sdgdsgsdg                                         ','dgsdg                                             ','dfgsdg                                            ','dfgdsg         ',1,1,1,1,1,'sdgsdg                                            ','dsfgsdg                                           ',1,'dsgsdg                                            ','sdgsdg                                            ',0,'                                                  ',0,'                                                                                                    ','dsgdsgsdg                                         ','dsgfdsg                                           ','sdgsdg                                            ','dsgdsg                                            ','dsgdsg         ',1,1,1,1,'dsgdsgds                                          ','dsfgdsgds                                         ',0,'                                                  ',1,'sdgsdg                                            ','sdgfsdg                                           ',0,'                                                  ','dsfgdsgdsgdsg                                     ','sdgsdgdsf                                         ','jkhgjhgj                                          ','jgjhgjkh       ','20000128 00:00:00.000','     ','fdghdfhdfhdfh                                     ','#odbc#she2003','kjgkhgjg                                          ','jkgkjgjkhgj                                       ','jkgjkgjg                                          ','kjkgkjgjk                                         ','jggjhgjkgjh                                       ','kjgkjghj                                          ','20000129 00:00:00.000','AAA','she2000             ','20000126 00:00:00.000','20000127 00:00:00.000','she2000                       ') SELECT TEXTPTR(brok_addr) FROM waste WHERE brok_addr LIKE '#odbc#she2003' 
go
-- 27/1/00 09:41:23.153 Duration 0.063, CPU 0.000, Reads 8, Writes 0
 
-- 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
-- 27/1/00 09:41:23.250 Duration 0.016, CPU 0.000, Reads 0, Writes 0
 
-- 27/1/00 09:41:23.250 SQL (ID=28, SPID=21, User=she2000(LEXWARE\PAULINE), App='', Host='PAULINE'(ffc5325d) )
ing characterLK waste.brok_addr 0x361400000000000001000000249B0300 NULL 0 WITH LOG
go
-- 27/1/00 09:41:23.250 Duration 0.000, CPU 0.000, Reads 0, Writes 0
 
-- 27/1/00 09:41:23.250 SQL (ID=28, SPID=21, User=she2000(LEXWARE\PAULINE), App='', Host='PAULINE'(ffc5325d) )
current charaLK waste.brok_addr 0x361400000000000001000000249B0300 NULL 0 WITH LOG
go
-- 27/1/00 09:41:23.263 Duration 0.013, CPU 0.000, Reads 0, Writes 0
 
-- 27/1/00 09:41:23.263 SQL (ID=28, SPID=21, User=she2000(LEXWARE\PAULINE), App='', Host='PAULINE'(ffc5325d) )
	Store ANSI vLK waste.brok_addr 0x361400000000000001000000249B0300 NULL 0 WITH LOG

References to the field waste.brok_addr continue until the log is full. We can't understand why there are so many references to this field, or indeed what these lines in the log mean.

Can anybody explain this ?

Best.

Matt.