I would second Paul's advice. Figure out if tempdb or the FT catalogs take more IO and move them. I'd be betting on tempdb, but check it.

I've never heard of it either, so I'm guessing typo.

Let us know if we're wrong.

Here's a great article from MVP Gail Shaw: http://www.sqlservercentral.com/articles/64582/

One thing you can think about is changing your process to commit at smaller intervals. If you can do that, the log...

What are you trying to accomplish overall? It sounds like mirroring might be a good solution for you. Only the active changes will move over.

I sent this thread to the publishing team today with a request for comments. I spoke with someone today as well about some of the ideas.

The disclaimer is likely something...

And there's the rub, we don't get to negotiate things, or get more choice. We also get what is negotiated, which definitely isn't always a good thing for consumers.

I think it's Fashion Friday. Haven't you seen my shirts? :w00t::-P

I think I'd agree with Lynn. most people I talk to at conferences don't see problems with getting articles that are controversial, or might not apply in many cases. They...

Thanks for the note. We try to fix these when we find them.

You can also use the "Report" button to let us know there's a formatting issue.

Me too! I think I'm one of those "less than great" ones.

I shall let that one slide because it's Tolerance Thursday :hehe:

The point is that the row number is relative to how the data is returned. There is no absolute row number.

I'm not saying you don't know anything, but rather that...

Yep, code tags changed. formatting corrected.

That's Ok, thanks for the note.

You can write a script that will do a waitfor, or even run a command in between updates

update a

set x = y

where month = 1

-- check errors

go

waitfor ()

go

update...