If this is something like an audit log that's accumulates GB of data and is only occasionally queried, then you want to consider inserting these records into an external file, rather than containing them in a database table. Database storage is a lot more expensive and problematic to manage than the file system, and this would keep your backups a lot smaller.

Below is a T-SQL solution that uses openrowset and the OLEDB provider for text files. In this example, the file sysobjects.csv should pre-exist in a folder on the database server or a network folder that is accessible by the SQL service account. The first row should contain the header, in this case "A,B". Also, to use openrowset, you need to have the server option 'Ad Hoc Distributed Queries' enabled.

insert into openrowset

(

'Microsoft.Jet.OLEDB.4.0',

'Text;Database=C:\TEMP\;HDR=Yes;',

'select A, B from sysobjects.csv'

)

select object_id, schema_id

from sys.objects