Were you executing it on the correct server, on the correct db?

What was causing the problem?

What did you change in the table definition?

One last trick...

Have you tried TRUNCATE / Full insert?

Truncate is almost not logged and the insert would have a lot of writes, but 0 work on the cpu.

Anyway you can setup replication?

I'm no expert at this but it may very well solve the problem.

One small thing may help here...

INNER JOIN ON ...  WHERE Source.Col1 <> Dest.Col1 --watch out for nulls here

That way you have less writes on the disk, but it's harder on...

If not in a cookie, this set of tables will solve your problem :

Reports

ReportId

ReportName

ReportsParameters

ParameterID

ReportID

ParameterName

Users

UserID

UserName

UsersParameters

UserID

ParameterID

ParamValue

Then just select those values from the db and overwrite the default parameters when they exist. ...

What was the problem?

Have you run DBCC checkdb?

Any other db integrity checks?

From the first line in the article :

Katie

SQLServerCentral.com, along with support from Red Gate Software and End to End Training, have been...

I can't really test this without some sample data on all tables. As far as my eyes can see, the trigger is not the problem... unless that trigger triggers another...

This runs perfect on my pc.

Do you have a trigger on that table that could throw this error?

Backup the DB.

Restore on another server.  Delete all the data you don't need.  Then run sp_spaceused.  It might be advisable to run dbcc cleantable if you have blob columns.  You...

Never heard of this, but maybe a workaround : have you tried backing up to a different folder then moving to that folder?

Why this is a quiet thread... I would have expected a few more comments by now.

I'd like to thank everyone who donated, I'm sure that'll make a big difference in...

You want the space used by a subset of data?