Really, never?

I find the percentage of the batch to be a pretty useful guide most of the time. Not all of the time, no, but more often than not.

Transactions on databases are generally short. Actually they should be as short as possible most of the time. That means a small entry in the log. That log gets truncated...

Not as such, no. I was just trying to get an understanding of how things were configured. If you're truncating on checkpoint, uh, I mean, in simple recovery mode, then...

I have nothing, but everyone around here enjoyed yours.

Purists are going to say at the database. I've mostly seen it done at the application level. You just have to make sure that the developers are with it enough...

Gail, you're just too good.

Everything Jack said plus...

Have you defragmented or rebuilt your indexes in recent memory? If not, I'd do that.

Have you examined the execution plan to see where the bottlenecks in the...

Well, if you're going to build it out... probably more than one table, even several. I say this because I know that blocking information, deadlocks, and trace/profiler, data are all...

Thank you again. Feedback, positive or negative, is always welcome.

Thank you, but Books Online is better and much more complete.

You're in Full Recovery mode and have log backups in place right?

Yes, that's normal behavior. As noted above, if there are multiple statements within a stored procedure, each statement will have an individual plan. Each plan will show as a percentage...

Definately a Books Online topic. I did write a primer on backups & restores over here[/url]. I'd still hit BOL first.

Flush the procedure cache, dbcc freeproccache(), and then rerun the queries. I think MANU might have it. You inserted one table from the other. It's indexes are going to be...

I would definitely start with the trace to see which procedures are running long because I'll bet they're the same ones that are causing this problem. There are some great...