Is it possible that the fillfactor changed when you did manual drop/re-create of the the indexes?   

I hope we see ultimately see resolution on this post because otherwise I'll have to doubt...

That looks good to me, maybe you do have physical problem w/the tape or the connection to it.

The RETAINDAYS should take care of not overwriting, shouldn't it?  Sometimes we manually...

run sysprocesses select as a task, then own spid is running from the server.  PS multiple NICs/addresses per server is not uncommon.

Are you using the WITH NOREWIND option?  This can make a huge difference when backing up multiple databases onto the same tape.  Only want to rewind when done for the day/session/tape/whatever.

Use dbcc page, as Amit says.  But bear in mind that unless you check immediately, things could have changed and something else might be on that page now.  I don't...

I am positive you will not improve performance by concatenating columns for the join. 

Why the join to Container_NCR (aliased as c)?  I don't see c being referenced anywhere.  Is this...

Or consider join on Actionlocation, ActionNum, CurrentYear and Revision as separate columns as alternative to computed columns--why would they have to be concatenated for the join?   Do you have indexes to...

I posted a reply last week, am sure I saw it here for a while but now gone. 

From quick google search I believe this behavior is MDAC dependent, so...

>> I'm ending up with 1/1/1900 in the status_date field doing it this way. <<

Neddyflanders, how are you getting this result?  I believe all of the people who've replied...

OK, sorry about my last post, got sidetracked into thinking about connection options.  I can duplicate this.  Try changing select in snippet a

Select *

to

Select @@trancount as "@@trancount", *

Seems...

I would check the physical disk object's various queue length counters to see if your disk subsystem is the bottleneck. 

This link contains a similar question & answer, has some good reference links: ...

This is an interesting problem.  I cannot duplicate, get the expected 1-row output. 

Your DBCC USEROPTIONS output pertains to your client connection settings--if using Query Analyzer then those connection settings...

You could eliminate the USE DB stmt entirely, specifying the target DB instead when executing the sp proc.  All master sp procs can be used this way, pretty convenient.  This yields one-line...

Another way to see ongoing status is RAISERROR with NOWAIT--these messages are output immediately.  In many of our long-running utility procs we use an optional @ShowProgress parameter with default value of 0,...

If you can afford it, keep the 1+0 for both log & data.  I've tested this, in an OLTP environment, results showed using RAID 5 for data performed noticably worse than 1+0.  As...