This sure does the trick, but please take into account that avoiding cursors is considered a best practice.

Generally speaking, cursors are slow...

It's a matter of pivoting your data (see PIVOT for more detail).

Try something like this:

-- Sample data

DECLARE @sampleData TABLE (

Idsint,

Name nvarchar(50),

...

Generally speaking, yes, but depends what "locations" means.

In order to increase performance, they must reside on different...

mr.zl8888 (6/5/2012)

---

Gianluca Sartori (6/5/2012)

---

You could use the parse function in this article[/url] and tweak it to return NULL in case a bad date is found.

However, that would require changing the...

GilaMonster (6/5/2012)

---

Gianluca Sartori (6/5/2012)

---

Dang! Two recommendations in less than three minutes.

If I had $.01 for every time I recommended this book, I would be...

Jeff Moden (6/5/2012)

---

From what I've seen of the banking crisis...

I would trace it with Profiler to see if some error is raised from SQL Server (and possibly ignored by the application).

Have you tried that?

Dang! Two recommendations in less than three minutes.

If I had $.01 for every time I recommended this book, I would be a millionaire!

I'm sure you're not going to like what I'll say...

"Fast" and "Slow", as well as "Good" and "Bad" are relative measures.

They must be related to a baseline, which is...

Charmer (6/5/2012)

---

Hi Friends,

How to copy tables from one server to another server?

i tried ssis and export/import through ssms....but it says server instance is timed out to get the connection....

since the...

You're welcome.

Glad I could help.

Thanks Lowell!

Glad you liked it.

High memory usage is not a symptom of memory bottleneck per se.

Did you set MAX SERVER MEMORY?

Did you monitor PAGE LIFE EXPECTANCY?

See this blog[/url] for more information.

You could use the parse function in this article[/url] and tweak it to return NULL in case a bad date is found.

However, that would require changing the function from ITVF...

Sorry, but I don't see where the problem lies.

Which records did you expect the query to return?