If you have an (extremely) large table(s), compress them [if on Enterprise Edition], particularly if they are (almost) never used, such as log/audit tables, etc..

First, you need an index on ceb.New_IndividualId: I'll assume you have that already.

Second, I'd cluster the #tmpIndividualCreateDates table by i.IndividualID: I'll assume you've done that already.

I guess the OUTPUT clause...

dwilliscp (5/14/2013)

---

Thanks for the warning Jeff.

On the Jobs front.. We almost never put SQL into the Job, but thanks for reminding me to check there too. Thanks to everyone...

I also search table sys.sql_modules, which contains the code for all sys.objects members of type P, RF, V, TR, FN, IF, TF, and R.

If you want to check for use...

When you delete a large or very large numberr of rows at one time, SQL Server defers the actual deletes. The next time a page with deleted r0w(s) is...

If the numeric portion is random anyway, definitely use all numeric characters if possible -- you're quite right: prefixing the random numbers with a fixed string will NOT help the...

jenny 12957 (5/6/2013)

---

hi,

im not sure this is the right forum to put this in, but i am working on redesigning our company database, and i was looking for best practices...

Just to clarify: with ROW_NUMBER(), you don't have to ORDER BY all the columns you want to SELECT; just one ORDER BY column is fine if that's all you need....

I think this will do it; performance will depend on the indexes available on the table:

select sales.*

from (

select distinct TerritoryID

from [Sales].[SalesOrderHeader]

)...

GilaMonster (4/30/2013)

---

No it doesn't. That would be an inefficient way of running a rebuild. Both online...

GilaMonster (4/28/2013)

---

1) DBCC DBREINDEX is deprecated, is included only for backward compatibility with SQL Server 2000 and should not be used any longer

2) Up to you. Depends on your requirements...

That could find the wrong entry and/or miss the entry if it was an index on a view instead of a table. Therefore, the code below is more robust:

IF...

I'd use a CASE expression so you can guarantee the order of execution; you don't need a CTE for that.

SELECT OBSVALUE

FROM OBS

WHERE 1 = CASE

WHEN...

Sorry:

SELECT

[values].value,

SUM(CASE WHEN Q1 = [values].value THEN 1 ELSE 0 END) AS Q1,

SUM(CASE WHEN Q2 = [values].value THEN 1 ELSE 0 END) AS Q2,

SUM(CASE WHEN Q3 = [values].value THEN 1 ELSE...

SQL_Enthusiast (4/25/2013)

---

Let's say, for whatever crazy reason, that temp tables are not an option. Is there a problem with using VIEWS? Especially if the views can be recycled for other...