General discussion


Full SQL Server log preventing import

By caseyx ·
Hi. I'm using SQL Server 7 on a workstation that is acting as its own database server, i.e. currently there is no connection to a database server on the network. I am a novice administrator as far as SQL Server is concerned, so I need a detailed solution to my problem.

I have been importing quite a few large files (up to 1GB) in Excel 2000 and plain text format into a SQL Server database. After a while, I started to receive error messages like the following from the import wizard: "Error at destination for row number 135271. Errors encountered so far in this task: 'The log file for database "nims_data" is full. Back up the transaction log for the database to free up some log space.'"

I've backed up the log file about 3 times but to no avail. I even tried truncating and shrinking the log but this had no effect. The truth is, as I'm performing mere imports and not actual transactions, I don't need the information in the log. I would be quite satisfied to delete or at least clear the log so that I can complete my imports. I invite your suggestions.

Thank you

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Related Discussions

Related Forums