SQL Kiwi (5/22/2012)

---

That...

Jeff Moden (5/22/2012)

---

Usman Butt (5/22/2012)

---

Sadly, as expected, it seems that things have not changed much. I have tried it on SQL 2012, and even after replacing the CHARINDEX function with...

SQL Kiwi (5/22/2012)

---

Usman Butt (5/22/2012)

---

Since, in the future, we may need the VARCHAR(MAX) version as well, I did some testing on the other solutions as tally table solution is a...

Gatekeeper (8/8/2011)

---

mark hutchinson (5/25/2011)

---

@Jeff

Here's an idea to kick around for varchar(max) data...use a tally table (or cte equivalent) to split the very large string into strings less than 8000 characters...

peter-757102 (3/15/2012)

---

Jeff Moden (3/15/2012)

---

peter-757102 (3/15/2012)

---

Jeff, did you receive any news regarding the performance characteristics of the code (or variations) on SQL Server 2012?

And on the extra bright side, in a...

peter-757102 (5/22/2012)

---

Too bad (for me) this new round cames at a bad time as I will be too bussy this week to particpate in this round of challenges.

As for bad...

EDIT:

Testing for VARCHAR(MAX) version was being done on SQL 2005 only.

/EDIT

Since, in the future, we may need the VARCHAR(MAX) version as well, I did some testing on the other solutions...

Hi,

I have used and referred the same splitter many times but need this to be implemented in a real time environment recently. So, I had to do some more research...

GilaMonster (3/28/2012)

---

Also note that just because SQL is using 7GB of memory doesn't mean it absolutely has to have 7GB to work. SQL's a memory hog, it will use whatever...

Congratulations for being one of the ever increasing admirers. No doubt, one of my favorite mentors.

Sorry have to edit it, as I did not tested it.

GilaMonster (3/28/2012)

---

Usman Butt (3/28/2012)

---

Yuri55 (3/28/2012)

---

"the OS will ask SQL to reduce its memory and SQL will do so, down to min server memory at the lowest. No one suffers, this...

Yuri55 (3/28/2012)

---

"the OS will ask SQL to reduce its memory and SQL will do so, down to min server memory at the lowest. No one suffers, this is the best...

The sure way to know the effect of MAXDOP setting is to test against your workload that involves parallel queries/operations. But for general guidelines, I would recommend this KB. This...

In that case SQL Server will suffer as the OS will move some SQL Server memory pages out of memory and into the (memory) page file on the disk, unless...