I don't think so.

"Agile thing" is to quickly bake a...

Indianrock (2/13/2016)

---

Thanks. I added the order by because the actual purge script is loading records into a temp table ( address_id ) and someone suggested that deleting by that order...

Indianrock (2/14/2016)

---

You're correct that the Address table may not be worth bothering with as far as purging. There are ten other tables such as these which have more delete...

I believe it's a perfect opportunity to address the issue.

I'm just trying to fix some purge jobs that weren't performing well.

ADDRESS

...

Deleting of addresses from database does not look like a bright idea.

There should not be such task in the first place.

It only makes sense if an address cannot be reused...

All my customers feel lucky. 😛

Orlando Colamatteo (2/11/2016)

---

Sergiy (2/11/2016)

---

Believe me, unfortunately - it's not.

Those who know what their...

wendy elizabeth (2/11/2016)

---

I have the following t-sql 2012, which is the following:

DECLARE @endYear varchar(04) = 2016

select convert(smalldatetime, ('07/31/' + convert(char(02), @endYear - 1)))

select convert(smalldatetime, '08/01/' + @endYear )

that is...

Believe me, unfortunately - it's not.

Those who know what their data types mean...

You need to post...

Change the type of trigger and your initial code will be just fine.

I'd only recommend replacing "IN" with an "INNER...

That's where following the clustered index order comes to play.

You lock the continuous chunk of data and remove it.

Minimal number of pages affected,...

Never ever use NVARCHAR(MAX) for column data...

JKSQL (2/11/2016)

---

OK so it is not a pass/fail. It is a Pass -> UPDATE SomeTable SET WHERE. That is what I was kind of thinking but wasn't sure. ...

Deleting by a single row is probably not the smartest idea.

The process by itself creates so much of overhead that deleting by 10 or even 100 rows may not affect...