On Jan 17, 5:21 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:
> (RodStron...@gmail.com) writes:
> > Sorry for the confusion in the last posting, I accidentally included a
> > line that is commented out. As I said, I kind of got tossed into this
> > one, and I'm trying to wade through and learn how everything works
> > here.
>
> OK. I had a vain hope that something more substantial was hidden for me.
>
> > I have a development version of this table, and things work fine in
> > there, with the same statement, so it leads me to believe there is
> > some inconsistency in the data,
> > as the number of records is not huge (~1000, ~300 international
> > records) and there appears to be no blocking going on.
>
> I will have to admit that I'm out of ideas. The only thing I can think
> of is that there is some corruption. You could run DBCC CHECKTABLE on
> the table, or DBCC CHECKDB on the entire database. I would not really
> expect anything to come out of this, but at least we could tick it off
> the list.
>
> --
> Erland Sommarskog,SQLServer MVP, esq...@sommarskog.se
>
> Books Online forSQLServer 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online forSQLServer 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Both the dbcc checks ran fine.

One thing that strikes me odd:
If I run the query through enterprise mgr, it completes very
quickly.

I'm looking at joining my live table(970 records) and my development
table(700 table), but I'm worried that the problem might just follow
the move.

Thanks so very much for your advice.