If you are looking to pause the flow of transactions from the distributor to the subscriber, then yes, all you would need to do is stop the subscriber job (distribution...

It is most likely that your login is not defined as a user in the Cheese database, or a member of a group that is defined as a user in...

LOB_DATA is not normally re-indexed, as it it can not really be indexed (except by full text indexing). Are these maybe included columns?

As you have probably found out already, the transactions to be sent to a subscriber in the distribution database are kept in a binary format. It may be possible...

Start by making sure you can ping the SQL Server.

If you can ping it, check to make sure the SQL Server service is running.

If it is, check to make sure...

Well, you will want to back up the FILESTREAM data as well at some point. While I have not tried it, I suspect you will get a lot of...

Ahh. Thanks, Gail.

GilaMonster (11/6/2013)

---

Matt Crowley (11/6/2013)

---

just keep in mind that a rebuild of the clustered index will involve rebuilds of the non-clustered indexes as well, so you may want to wait for...

You may want to set up a simple profiler trace with just the RPC Completed, and T-SQL completed events being monitored. Run that for a while, then save the...

I would run a DBCC CHECKDB against the restored copy (probably off hours, as this will hit the disk pretty hard), just to be sure everything is correct with the...

If you set up a witness, you should be able to get the secondary running when the primary goes down for a long enough time (the witness has a timeout...

I am not sure that heaps are a particularly good target for defragmentation. by their nature, they are not ordered in any way, so page splits should not be...

Break it into two stored procedures (you can have a single stored procedure call them both in succession, if necessary). The first procedure should only do the truncate with...

Is the original log file from the original server available? Or did it "go down with the ship"? From the error messages, it seems you have copied over...

Only one other thing to add to this, just be sure you are migrating to an Enterprise edition SQL Server, as I do not believe that compression is supported in...