That's damn hard to do in SQL Server. Full text will probably be your best bet, but likely to be hard even with that.

No where near enough information.

Can you at least post the query, that may give a starting point. Also, what exactly do you mean by 'wrong result'? Wrong in what way?

Grant's blog was linked in the first reply.

Enterprise Manager's not going to be able to connect. I'll be surprised if it can even connect to SQL 2005, much less 2012.

Why are you still using 14 year old...

Rebuilding an index updates the statistics on that index. There's no need to do it again, unless...

Could you be a bit more specific about what 'they' want?

All posts have always had an edit button.

The part where they're going to a broken site is new, they used to just reload the thread.

No ORDER BY, no guarantee of order. End of story.

It will enable the new cardinality estimator, which could easily have caused what you see, if the DB had been on compat mode 110. Since it's not, we can eliminate...

Bear in mind that in 2008 Management studio didn't show the spill to TempDB warning. Only from 2012 is that warning shown.

Pull out Profiler, trace for hash and sort spills...

Grant Fritchey (10/16/2014)

---

I'd raise a stink internally. You can't work miracles. There are physical limitations to the universe and a query without a WHERE clause is going to smack right...

If a transaction rolls back, all data modifications done within the transaction are rolled back. Even if they're in different databases.

Time to get management involved?

And hope they...

Order of columns in a table has no meaning. Just let them go at the end and, if you want them selected out at the beginning write your select statement...