SQL CHECKSUM as a way to index a large text-oriented table with frequent INSERTS and ocaasional SELECTS?
I have a SQL Server 2008 database table that accepts auditing information. This information is primarily text-based but has a numeric field that acts as a foreign key for SELECT operations. Most of the activity on this table is INSERT-based (no UPDATES though) with an occasional [SELECT WHERE] query to generate reports.
Currently there is a numeric IDENTITY PK autonumbering column with a clustered index on it. The table is constantly growing, nearing 1 million rows, and my concern is that INSERT performance will degrade over time due to index updating,etc.
My question is 2-fold:
1) Is there any benefit to even having an index for this table given the nature of the activity it receives?
2) If an index IS used then would a CHECKSUM column based on the other fields be a candidate for a non-clustered index without adversely affecting performance?