Latest version of SQL prompt can do that too....

Absolutely not.

There's 5 posts on my blog on the subject if you want the full detail.

WHERE EXISTS, not IF NOT EXISTS

Very, very, very slightly more efficient.

Yes.

That sounds more like a server-scoped DDL trigger.

PBM is for enforcing policies (like ensure no databases are named in such a way, ensure all databases are in full recovery, etc)....

rrn 62873 (11/20/2014)

---

Using Ola's solution, I have now set up a solution where the production database gets maintained (DBCC and index rebuild/defrag) every saturday, differential backups every four hours and...

You test your application against a test database that's already been upgraded, you identify any issues and you fix them. Once the tests run clean, then you update the compatibility...

By testing before you make the change.

To be honest, performance is irrelevant in this case.

If you need all the rows from a large table and matching rows from a small table, then LargeTable LEFT OUTER JOIN...

It won't generate anything and there are no checks done when you change the compat level.

I've been sitting with negative leave days available since July (about -0.5 at this point). No one in management is complaining, no pointed hints that I need to work more....

Koen Verbeeck (11/20/2014)

---

GilaMonster (11/20/2014)

---

Your table is too wide. The fixed length columns in a table (data types other than varchar/nvarchar) cannot exceed 8060 bytes total. Your table is so large...

The DMV above just shows averages of what's in the plan cache, not exact executions of each query. That may be good enough, it may not be.

Have a read through...

ramana3327 (11/19/2014)

---

That is not related to parameter sniffing.

Why because we are passing 3 input parameters. Those are default parameters. We are not changing either in SP or Report also.

Just tested...