>>
>>No, just one or two records at a time. Maybe up to 10 every now and then.
>>
>>So, is it OK in this scenario?
>
>In that case, I would say yes. I think the performance issues are far more due to either an unoptimized query in the EXISTS part....or a locking issue associated with that query....or high fragmentation in the table due to the uniqueidentifier.
>
>Again, if you discover fragmentation above 30% on that table, I would try to set up a regular reindex job

I got VERY high fragmentation on the indexes on the 2 tables I have been generating test records for. Both are above 99% average! Of course I'm trying to re-index like this:

EXEC sp_MSforeachtable @command1="print '?' DBCC DBREINDEX ('?', ' ', 80)"
GO
EXEC sp_updatestats
GO

and I get this error:

Msg 1101, Level 17, State 1, Line 1
Could not allocate a new page for database 'RESREPRICERTest' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

and this one:

Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'sys.sysobjvalues'.'clst' in database 'RESREPRICERTest' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

Strange, I have 200GB free on my C: drive and 157 GB free on the drive where the database files are. The database is just about 10GB. Hmmm, this is the express version and I know that's the size limit, I wonder if that is why I'm getting the error.