Elliott W (9/15/2009)

---

I guess we'll have to agree to disagree, my experience has shown the opposite. So the moral of the story is test both, use what works for...

kjs714 (9/15/2009)

---

In the sample, you are using a batchsize of 10,000. This will end up causing a table lock unless the escalation gets blocked by other processes. If table locks...

Yep - go with int like I originally said 😀

I must say I found the complete opposite...

No worries.

Bear in mind smallint will only do you for up to 32,767 records before the IDENTITY field wraps round to -32,768.

Use smallint only if you are *sure* the DB...

I've just gotten to the end of a long project doing exactly that. And it's not an easy thing to do. I started out about 2 1/2 years ago, thinking...

look at the help for CONVERT and see if you can provide a style code.

If you have the option to use the CLR for that, then do.

string[] parts = String.Split(input, new char[] { '-' });

return (parts.Length > 3) ? parts[3] : string.Empty;

mm (9/15/2009)

---

Heh - snap...

SELECT DISTINCT CRM_Orders.TRANSACTION_ID,

CRM_StatusCodes.USER_STATUS,

...

Ok - it sounds to me like you want to know about how to use AND and OR.

This example is entirely silly - but there you go:

If I want to...

I have two things to say:

1) You seem to have all your primary keys as Char() fields. Unless there's a compelling reason for that, go with int, or bigint if...

Chad Crawford (9/15/2009)

---

Where appropriate, disabling indexes can help boost delete speeds as well. I frequently create a "pared-down" database with a small subset of records. Since no one...

Lynn Pettis (9/15/2009)

---

Okay, I missed it the first time, but he did say ABOUT 100,000,000. That leaves the actual number of rows to be deleted open for interpretation. ...

He did say there was a...