Cumulative Updates are, well... Cumulative Updates! 🙂

The first line in the KB article for CU6 should be clear enough:

Cumulative Update 6 contains hotfixes for the Microsoft SQL Server 2008 R2...

Only CU1 to CU5.

This KB article explains it all: http://support.microsoft.com/kb/2567616/en-us

Glenn Berry has a nice post on the subject:

http://sqlserverperformance.wordpress.com/2012/07/27/sql-server-2008-r2-service-pack-2/

Thanks for the link, Wayne.

It could look like...

Lynn Pettis (8/10/2012)

---

Okay. Just let off a little rant to Mr. Celko again. Please, if anyone thinks I went too far (and no, you'll have to find it...

Ah, great. Thanks Anthony.

Sorry, can you rephrase? I don't think I understand what you mean.

Weird, I always...

I suggest running CHECKDB more often than you're doing.

Taking a backup of a corrupt...

Here's an example:

DECLARE @ErrorMessage NVARCHAR(4000)

DECLARE @ErrorSeverity INT

DECLARE @ErrorState INT

-- CREATE A TEST TABLE

IF OBJECT_ID('tempdb..#test1') IS NOT NULL

DROP TABLE #test1;

CREATE TABLE #test1 (i INT PRIMARY KEY);

BEGIN TRY

...

This is the solution I had in mind.

If you feel confident, try it. If it was my database, I would restore from backup.

Don't run profiler. Use sp_WhoIsActive or something similar to find the offending query.

If CPU is hitting 100% I'm pretty sure adding more memory won't help.

You seriously need to find what sends CPU to the roof. It could be a runaway query that...

No way, AFAIK.

If you need such a feature, then take a look at Visio.

A free alternative is DB-MAIN or ER-Win Community Edition[/url].

Kwisatz78 (8/9/2012)

---

We do apply it to test at first and know that it is going to break replication. The ERP releases are more important than the work required to...

Looks like logical corruption.

I would restore from backup if possible.

There's another method, but I won't disclose it unless you have no backups.