Or:

EXEC sp_helptext 'derived.Case_Times'

You don't reorg/rebuild every index every week do you? You do have some type of check so that you rebuild only tables that are severely fragmented?

If you're already doing...

It's not a function, as there are no parentheses, (), after its name.

This code will tell you what it is, in the "type_desc" column:

SELECT o.*

FROM sys.objects o

WHERE

...

Jeff Moden (1/19/2015)

---

ScottPletcher (1/19/2015)

---

I still see no reason to risk @@ROWCOUNT if you just want to know if a row was modified or not -- that easy enough to check...

Jeff Moden (1/19/2015)

---

ScottPletcher (1/19/2015)

---

For best overall performance, review "missing index" and index usage stats from SQL Server, then determine first and by far the most important: do you have the...

You could also defer decoding/lookup until after the counts are computed. This might make the final query more "natural-looking":

Select

age.[10_Year_Age_Band],

epi.count

From (

...

If you are on Enterprise Edition, you can do online rebuilds of most indexes, depending on the data types appearing in the index.

For best overall performance, review "missing index" and index usage stats from SQL Server, then determine first and by far the most important: do you have the best clustered index...

I still see no reason to risk @@ROWCOUNT if you just want to know if a row was modified or not -- that easy enough to check with EXISTS(), which...

Jeff Moden (1/19/2015)

---

ScottPletcher (1/19/2015)

---

@@ROWCOUNT is no longer reliable in triggers and should not be used to determine if/how many rows were affected. You have an easy alternative anyway, since...

Do not use INFORMATION_SCHEMA.* views in SQL Server. They are very slow compared to sys.* views and seem to cause much more locking/deadlocking. Based on research, it seems...

@@ROWCOUNT is no longer reliable in triggers and should not be used to determine if/how many rows were affected. You have an easy alternative anyway, since you just want...

You could check for ascii 0 in a the column like so:

WHERE

col1 LIKE '%' + CHAR(0) + '%'

Why would either be "needed"? Just...

halifaxdal (1/16/2015)

---

Lowell (1/16/2015)

---

halifaxdal (1/16/2015)

---

no way i know of to ignore errors, you have to explicitly use LEFT functions in the SELECT or something to work around this issue.

based on your...