As the error clearly says, it's a unique constraint. Therefore the constraint has to be dropped and recreated.

Insert a new row?

So, if the user selects all 25 columns one by one, then you want to have 25 separate rows in the database table, each with a single...

Something's blocking the drop index. Identify what that is and either wait for it to finish or kill the session. Then drop those indexes and recreate them.

Do it in code,...

What are you trying to do?

Of course that's going to insert the value twice, there's no conditions around the insert. The WHERE is just on a select of the parameter,...

Drop the indexes. Recreate them. Don't rebuild, it won't fix anything. You have to drop and then recreate.

Nothing. Same as I suggested last time, and the time...

Please post the rest of the output of CheckDB.

Do the restore from T-SQL, post the exact error message.

Only writes to the log are synchronous. Writes to the data file happen later.

Sure. File in filegroup 1 on disk 1, file in filegroup 2 on disk 2. However a table (or at least a partition) must be in a single filegroup.

this...

Sure, once I've found a few hours to sit and investigate the scenario you're describing, figure out what's happening.

The log is not an audit trail, don't try to use it...

Re inserts.

Once over a few pages (8 or 24, can't recall), SQL allocates dedicated extents to tables. So 8 contiguous pages. So what's happening probably is 8 pages from one...

He corrected that statement in a later post

msmithson (3/14/2014)

---

Sorry I wasn't...

I'd have to sit and play with the log for a few hours to figure out what you're describing. It's not documented at all, it changes from version to version,...

And when you run the proc from SQL as I suggested?

Those are compile-time warnings, not interested in compile-time messages, interested in the run-time errors (if any) from SQL Server.