The things you mention don't typically cause the crazy increase you speak of.  And I just told you a "good way" to find it so someone can...

The things you mention don't typically cause the crazy increase you speak of.  And I just told you a "good way" to find it so someone can fix it....

Crazy increases in size are normally due to a query that has one or more "accidental Cross Joins" in the form of "Many-to-Many" results.  They typically contain a DISTINCT...

For best overall performance, it's extremely likely that you need to change the clustering index on the table to be ( OrderID, ItemID ).  Especially if the table is...

I think I can help with that one.

IDX1 would have the 3 columns with the data ordered by OrderID, then ItemID, and finally Status.  If there were more columns...

thank you !

if I create the following on the table , could you please tell the...

Waiting for locks is normal in SQL Server (or any other relational db).

Whether the waits are excessive is a different q.

Since you've provided no details, to reduce bad effects...

Locks are a required part of SQL Server.  You wouldn't want 2 queries updating a single piece of data at the exact same time.  Much better for them to...

Thank you Adi Cohn for your kind help!

It will show you details only on plans that exist in the query cache.  As soon as a query plan is being deleted from the query plan, you won't...

Ah, but it appears that may be operating under a really bad premise.  Changing a VARCHAR(200) to a VARCHAR(100) will, by itself, DO NOTHING to save on space.  The...

Thank you but the question above is...

Thank you but the question above is basically just...

we can use sp_spaceused to know how many space reservred by a table and know how many spaces for data space and index space, but if there is...

Thank you Anthony.green!