You say the SQL gets "built on the fly".

Can you post an example of the exact SQL that gets built.

In what way does it fail?

AWE memory usage doesn't show up in task manager.

Use DBCC MemoryStatus, or the perfmon counters 'Target Server Memory (KB)' and 'Total Server Memory (KB) to see how much is actually...

I should have looked at the original post in detail.

Although you can use the INSTEAD OF trigger to replace data in columns, the nullability is checked BEFORE the trigger is...

Hmm, strange. Just thinking of things to try:-

If it worked when it was added using QA, but not SSMS, what happens if you drop the trigger in SSMS and re-add...

There's no problem with the INNER JOIN, it's the TOP 100 PERCENT that it's complaining about.

Why do you need the TOP 100 PERCENT?

You don't need to do anything... the 62.8 GB of reserved space is the sum of your data (26.8 GB) plus the indexes (35.9 GB) plus the unused space (17mb)....

Are you certain the trigger isn't firing?

Add a print statement as the first statement of the trigger just to verify this.

Is it the database or the transaction log that is growing?

I've seen this a few times before on SQL 2000.

The recovery model for the Distribution database is "Full", and although...

If you only select the columns you want, you will be returning less data (obviously).

Also, SQL Server may be able to get the columns you want from an index, without...

I'm not sure I fully understand your schema and/or requirements, but this may be what you are after:-

SELECT

Company.iCompanyID AS Company_ID,

vchCompanyName AS Company_Name,

Company.iPhoneTypeId AS Company_PhoneTypeID,

Company.vchPhoneNumber as Company_Phone_Number,

p417.vchPhoneNumber...

... or ER/Studio

Or look at Jeff (RBAR) Moden's article:- http://www.sqlservercentral.com/articles/TSQL/62867/

I don't know if you will find a statement from Microsoft, but the SQL standard says that if you don't use an ORDER BY, the server may return the results...

Unless you use an ORDER BY, the sequence is not guaranteed.

SQL Server will choose what index to use based on the actual query.

If you were to add a WHERE clause...