How many rows do you add in a day? Is the fragmentation really significant enough that you need to rebuild a table with 1.2B rows?

Who knows, maybe this?

select id, name,

max(value) as value

from table A

group by

id,

name

Highlight the text, then press Ctrl-Shift-U. And, yes, Ctrl-Shift-L will convert everything selected to lower case :-).

Edit: That's in SSMS (just to be clear).

First off, switch to using BEGIN TRY ... END CATCH rather than just the error code. That will give you a lot more options and capabilities on your error...

Look up the "READPAST" hint. I think it may help with what you are trying to do.

For non-work days, I agree a table is best, and as I stated above, I have tables holding non-work dates (only). Such a table is naturally much smaller that...

Van Heghe Eddy:

Keep in mind that when SQL creates an index on a table, there are basically two types of pages in that index: upper-level (non-leaf) index pages and lowest-level...

Indeed, and that's exactly what I pointed out. Shrinking before...

A shrink will not save any (significant) space in the db backup, but it certainly can make the restore files smaller.

You could also consider restoring the db back to its...

Be aware too that if @DataSourceJobRevenue is NULL, then nothing will print, because

PRINT NULL

doesn't show any output.

whenriksen (10/18/2016)

---

I rewrote it yet again, without case or firstdate:

DATEADD(WEEK, ABS(( DATEDIFF(WEEK, '20161009', DATEADD(DAY, -1, o.modify_date))

+ 1 ) % 2), DATEADD(DAY, ( DATEPART(WEEKDAY, DATEADD(DAY, -1, o.modify_date))

- 7 )...

Fortunately SQL stores the last good DBCC date in the header data for the db.

Run this command:

DBCC DBINFO('<your_db_name>') WITH TABLERESULTS

And look for a "Field" value of "dbi_dbccLastKnownGood" (or similar): the...

The value for @DataSourceJobRevenue must be passed in as a parameter value when the proc is run. For example:

EXEC dbo.ImportJobRevenue 'JobRevenueValue'

It's a required parameter, so its value must be...

It might be worth trying code below, as it seems to limit the number of "j" lookups required. A nested-loop join didn't prevent the extra lookups -- for whatever...

whenriksen (10/17/2016)

---

ScottPletcher (10/17/2016)

---

Rather unfair to cut off the part where I asked what specifically are your requirements, because you've never stated them clearly, and then to blast me for not...