Heh, you too.

GO is just a command to the Client SQL program (Query Analyzer, SSMS, etc.) to terminate the current batch and execute it. Go does not terminate the current session...

Try it for your self:

create table foo(bar int)

GO

select * from foo

Begin transaction

Insert into foo select 99

Select * from foo

GO

Select * from foo

Rollback transaction

Select * from foo

GO

Select * from foo

GO

Drop table...

Hmm, this is very interesting, can you post the query that is CPU bound?

Yes, that is not hard at all. But it is not what the...

GilaMonster (8/14/2008)

---

Other possible suggestion is to remove that table from the publication entirely. Put it back in after you've finished the deletes. That means that log records for that table...

The problem is that in a Replicated environment, it takes both Backup and the LogReader to release a replicatable record from the LDF. Well, if you're in Simple mode,...

I...

Actually, stopping & disabling the LogReader Agent will also stop and disable the Job. (in fact it may be the same thing).

I ask the above question, because I have had that happen to me: Doing a massive insert/update/delete, and the LogReader starts trying to scrape the log while the transaction...

OK, there are several places that you can do this from, but the best place is: "Replication Monitor/Agents/Log Reader Agent" which will all of the LogReaders and only the LogReaders....

Now, now, be nice to the OP, Gail. 😀

If it is Transactional Replication, then you (Stop & Disable) the LogReader job (from the Replication Interface, not the SQL Agent). This is the job that scrapes the Log...

Good point. I'll remember to reference my base arithmetic system in the future :).

Use the MAXERRORS option. Or else a Format file.