This might stimulate some ideas:

https://www.google.com/?q=publicly+available+data

Users will complain, that's the steady-state of the universe.

Identify the actual cause of the performance problem and work on fixing that. Then the users might stop complaining for a nanosecond...

You might be working under a misconception around shrink.

It's not compression or anything similar. It's not something that has a persistent state. It's not something where you can say 'this...

Recovery model has nothing to do with performance. It's about recoverability.

If you need to be able to restore a DB to point-in-time, you need to be able to restore to...

Please don't start multiple threads for a problem people are already helping you with.

No replies to this thread please, direct replies to http://www.sqlservercentral.com/Forums/Topic1566066-2799-1.aspx

Please don't start multiple new threads for single problem.

No replies to this thread please, direct replies to http://www.sqlservercentral.com/Forums/Topic1566066-2799-1.aspx

Table definitions, index definitions, the query itself and the actual execution plan (not estimated)

Ignore the CX packet and tune the query. Look for waits that the query incurs other than CX packet.

If you want specific help, please post the query, table and index...

Shameless self-promotion: https://www.simple-talk.com/sql/performance/sql-server-deadlocks-by-example/

Yes. It's a value like any other.

Does sql server still order the records based on these keys? (Clustered index)....

Assuming it's a regular problem and not suddenly today it's slow when it's usually fine...

I'd run a server-side trace and do the analysis that was described in the article you...

Maybe start with google, there's a huge amount of information available, and if you have specific questions ask?

Once the statement completes and any triggers on the table have fired and have completed.

Why on earth would you do that?

There's nothing in what you show to go on. In...

Nothing to do with a procedure.

Locks taken by data modifications are released when the transaction finishes (commit/rollback). If you aren't using an explicit transaction, that means the locks are released...