Lowell (12/18/2012)

---

GilaMonster (12/18/2012)

---

I recommend restoring from the last good full backup. Since the DB is in simple recovery model, that amount of data loss (since the last full backup) must...

I recommend restoring from the last good full backup. Since the DB is in simple recovery model, that amount of data loss (since the last full backup) must be acceptable...

If you repair, you will lose data.

If you want to avoid data loss, then you need to take a tail-log backup, restore the last clean full backup and all log...

Restore from a clean backup.

Or you could save the expense of a completely unnecessary tool, as all that will do is call...

Ok, So Memory/pages\sec

That's the count of hard page faults (page faults/sec are soft page faults). That's to do with pages that are in virtual memory but not physical memory (ie...

SQL doesn't keep track of how it's licenced, that's paperwork. (other than SQL 2012 in one case)

As for server name, version and edition, have a look at the MAP tool...

Which pages/sec? Under which section? There are multiple pages/sec counters in different sections and they mean different things.

Since...

Sure it's possible. It's just going to be a normal merge replication setup.

32 bit or 64 bit SQL?

Whilst i was in perform i noticed the...

Huh?

LOB = Large Object. Nvarchar(max), Varchar(max), varbinary(max),...

Why are you ending up with so much free space that's not going to be reused?

No, it's just that LOB columns massively slow down shrinks because of the way they pages link together.

DBCC Shrinkfile is the only way to release unused space back to the OS.

Let me guess, either lots of heaps or lots of LOB columns?

Any way you like.