You might not want to go down that road, and I don't blame you, but you might have to. Are you doing full scans on the statistics or just using...

Why would you want to do something like that?

Follow Stephen's advice. Use the MAX data type and keep working with sp_executesql if you have to do dynamic queries.

Can you post the query and an execution plan? That would help. Also, can you show the STATISTICS IO and STATISTICS TIME for the query?

Nice to know you figured it out. Thanks.

OK. I'm stuck. I assume you've run a consistency check? Can you query the table through the INFORMATION_SCHEMA.TABLE view?

How about a refresh? Was it created recently?

Two possibilities come to mind. First, there's some sort of security issue, the object is in a different schema which you don't have access to, but the TSQL is logged...

No, not really. Without a log backup of some sort, there's nothing to restore from for point in time recoveries. You have to set up maintenance.

Dan Colbert (2/11/2009)

---

Grant,

Sorry for the delay, here's the connect link https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=410537.

Michael,

Try connecting to the 2005 SSIS in SSMS 2005. I think you'll find it connects to the proper version....

Yep, it's like Lowell says. Most of the time temp tables are so small that even putting indexes on them and getting the index used in the execution plan doesn't...

I would go with a single Address table and then join tables to the different entities that use it. This allows you to have a single source for address validation...

Ah, SQL Server 2000, you need to follow Steve's advice then.

BTW, this is the SQL Server 2005 forum that you posted in. You will get different answers to questions depending...

Based on the structure and the statement, this sounds like homework. What have you tried so far that hasn't worked?

dbo is a system schema. It can't be changed. You just need to add a schema and then make it the default.