Yes, it's true.

If absolutely necessary, create a nonclustered index(es) on the GUID(s).

If Change Tracking is enough for what you need it, use it, as it's less overhead than either CDC or a trigger. And it doesn't require Enterprise Edition.

First, you need to create all the logins on NM that are used in the db you copied there. You can script out the logins from the old server,...

You don't have to grant each procedure separately, you can grant execute on the schema (or for the entire db, no matter what the schema, if you prefer). The...

What's proposed here is a really poor practice. You can't just arbitrarily shrink a SQL db log with no analysis because you could just be forcing it to be...

TheSQLGuru (8/8/2014)

---

ScottPletcher (8/8/2014)

---

TheSQLGuru (8/8/2014)

---

ScottPletcher (8/8/2014)

---

My first choice would be to use RECOMPILE and just force SQL to rebuild a plan every time.

But, if a HASH join is the "good" plan,...

TheSQLGuru (8/8/2014)

---

ScottPletcher (8/8/2014)

---

My first choice would be to use RECOMPILE and just force SQL to rebuild a plan every time.

But, if a HASH join is the "good" plan, forcing a...

My first choice would be to use RECOMPILE and just force SQL to rebuild a plan every time.

But, if a HASH join is the "good" plan, forcing a HASH join...

Robert klimes (8/7/2014)

---

So now...

Seems to me it would...

Unfortunately, you really can't accurately look at one index recommendation in isolation. You really have to consider indexes in toto, including a minimum of missing index and existing index...

A longshot, but, in the interests of being thorough ...

Are there possibly different "table1" tables under different schemas? Could one session be reading from a different schema.table1 than the...

select 18 * 1.0/94

Yep, sure did :blush:

The INSERT could fail if it ran out of physical file space to hold the new rows.