MyDoggieJessie (1/25/2013)

---

And Yes, changing the job name itself would still cause an issue, however hopefully changes like that would be made by a DBA or otherwise communicated that a change...

MyDoggieJessie (1/25/2013)

---

newdba_sql (1/25/2013)

---

Yeah... For somereason I was putting job name but not the job id......:w00t:

So this script will check if the job's last run status is successful, then it will...

Sean Pearce (1/25/2013)

PLEASE NOTE: You have not aliased all your columns so I have no idea which tables they come from. You must edit the following queries to remove any...

Of course if you just code your dates as 'YYYYMMDD', conversion always works, and you don't have to waste a second on any of that other garbage.

The two big advantages of computed columns are:

1) a consistent definition;

2) defined in...

Lowell (1/24/2013)

---

i thought it was clear: i read it as howard saying there is no need to mark an calculated column as persisted in order to index it...it's not a...

An extraordinarily large table (which I'll abbreviate "xlt" for convenience) can indeed cause unusual issues.

If you use tempdb, it needs (lots of) extra disk space, which basically can't be freed...

ISDATE() is reliable for what it claims to...

Then you've got a second issue that needs addressed! 🙂

Increase the size of tempdb until you have "slack" except...

HowardW (1/24/2013)

---

ScottPletcher (1/24/2013)

---

HowardW (1/24/2013)

---

ScottPletcher (1/24/2013)

---

That's not necessarily always true. You might persist a column if its...

HowardW (1/24/2013)

---

ScottPletcher (1/24/2013)

---

That's not necessarily always true. You might persist a column if its requires significant...

You can use CASE w/i a GROUP BY.

You can also use CASE w/i a SUM to control which values get aggregated. For example:

SELECT

a, b,

...

HowardW (1/24/2013)

---

SQL* (1/23/2013)

---

Hi All,

While reading about Computed column if found that if we mentioned PERSISTED Key word while creating/altering table then we can create index. But i'm able to create...

IF and only if ABC.COLUMN2 is a (very) large column, and ABC.COLUMN1 is used by itself a lot, it might be worthwhile to keep both indexes.

You should also review sys.dm_db_index_usage_stats...

You need to get rid of the massive GROUP BY; you should be able to do the SUM() in a subquery rather than the main query, but I can't be...