Patti Johnson (9/4/2013)

---

I have added what was suggested:

IF DATABASEPROPERTYEX('archer', 'Status') = 'ONLINE'

BEGIN

use archer

SET NOCOUNT ON

END

It looks good until you execute and I...

Try this:

IF DATABASEPROPERTYEX('archer', 'Status') = 'ONLINE'

BEGIN

...

END

You don't want to use a function against the END_DATETIME column if you can avoid it, since any function will prevent SQL from using the full seek capabilities against that...

Don't forget restore damaged instance. That is the most complex recovery. Particularly test for master, model and msdb.

Whatever rules you decide on, you should enforce them programmatically. Otherwise, the rules will be broken and be meaningless.

Also, follow the first rule of naming -- don't build meaning...

Something like below. It's possible you only need one left join, depending on the specific data in your tables:

SELECT

CASE WHEN b_out.Continent_cd IS NOT NULL THEN...

MyDoggieJessie (8/30/2013)

---

ScottPletcher (8/30/2013)

---

LOL. That's self-contradictory...

Sean Lange (8/30/2013)

---

ScottPletcher (8/30/2013)

---

Sean Lange (8/30/2013)

---

ScottPletcher (8/30/2013)

---

Sean Lange (8/30/2013)

---

ScottPletcher (8/30/2013)

---

To me, that's not a logical claim. While NOLOCK is clearly...

Sean Lange (8/30/2013)

---

ScottPletcher (8/30/2013)

---

NOLOCK can be useful, for example, for code lookup tables, such as state code lookups. A state hasn't been added since 1959, I think I'll risk...

Sean Lange (8/30/2013)

---

ScottPletcher (8/30/2013)

---

Sean Lange (8/30/2013)

---

ScottPletcher (8/30/2013)

---

To me, that's not a logical claim. While NOLOCK is clearly dangerous, it DOES...

LOL. That's self-contradictory -- if NOLOCK avoids...

Sean Lange (8/30/2013)

---

ScottPletcher (8/30/2013)

---

To me, that's not a logical claim. While NOLOCK is clearly dangerous, it DOES in fact reduce...

You should be able to use a correlated subquery, like so:

SELECT

@mystring,

REPLACE(@mystring, name, value) AS newstring

FROM (

SELECT TOP...

Here's a quick-and-dirty first try -- might or might not work. Also, you need to get rid of the DISTINCT if at all possible -- it's a big drag...

To me, that's not a logical claim. While NOLOCK is clearly dangerous, it DOES in fact reduce overhead by avoiding...