While I see the flaw in the question, folks don't have to be so mean pointing it out -- that sort of feedback would certainly keep me from offering up...

Shrinking a log file (a bad thing in general to do) will have its results dependant upon whether the log backup has been taken and the pertinent log file truncated...

Without that other log backup you are hosed. You either have to get that other backup file and apply it somehow or start over and redo log shipping with...

STANDBY allows you to do read-only queries against the data whereas NORECOVERY is completely offline. STANDBY requires the .tuf file to manage its use. I have never seen...

OK, so it wasn't just me staring and trying to decide between "error" and "4" then. Finally picked "4" because that error wouldn't be the GROUP BY error.

If only it were just a growing log file. We have separate files for very large tables on separate LUNs and spindles, and I found that those files double...

SSIS menu -> Logging.

That one WAS an SSIS failure; you are past the previous error. At this point, best I can tell you to do is set the package to log its...

Speaking not about the product but the idea behind the editorial, I can't tell you how painful the size issue is. It causes reindex havoc for me because in...

It's not the package that needs to change, it's the job proxy. This is a server config issue. A proxy is used to give an execution environment for...

If sp_who2 shows it as running, it's running, and you have no errors -- it's running.

If it is taking much longer than usual, first thing I can think...

How big is your database? How long does it normally take? Do you have errors? It could simply be that it takes that long. I/O and...

Just re-read the original question, I agree with Gail it's non-clustered to clustered. OK, if you have PRIMARY KEY NONCLUSTERED you are in my opinion where you want to...

Yep, this is why I NEVER use PRIMARY KEY CLUSTERED even IF I intend to cluster on that column. I am willing to burn the index space and index...

There is no way to say without seeing the code that is failing. Without that I would guess that you have search queries without ORDER BY in it that...