>I am 'porting data from a VPF table to a SQL Server table. The VFP table contains around 300,000 records. To do this, I have a remote view to the SQL Server table and I simply do a SCAN on my VFP table and do an INSERT INTO for each record.
>
>Every 50,000 records or so I get an ODBC error,
>
>"Cannot allocate space for 'Syslogs' in database 'DatabaseName' because the 'logsegment' is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment."
>
>I did a DUMP TRANASACTION WITH NO_LOG and this solved the problem, until I added another 50,000 records and it happened again. Is this just a case allocating more space somewhere (where?), or should I somehow stop SQL from logging the operations?
>
>Any help would be greatly appreciated.

Hi Steve,

I think the problem is that the data is being sent in one big transaction. I may be wrong but the transaction log is certainly being filled up. As you are only sending data to the server as part of the installation and not using it in an application, I suggest you turn off the Transaction log for the database till the data is transferred.

You do this by editing the database in enterprise manager and clicking 'Truncate Log on Checkpoint' in the options page

HTH