Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Chris_Kelley
Posting Yak Master
114 Posts |
 Posted - 2014-08-22 : 09:04:14
|
| c |
|
|
Chris_Kelley
Posting Yak Master
114 Posts |
Posted - 2014-08-22 : 09:10:02
|
| c |
 |
|
|
Chris_Kelley
Posting Yak Master
114 Posts |
Posted - 2014-08-22 : 09:34:36
|
| c |
|
|
|
gbritton
Master Smack Fu Yak Hacker
2780 Posts |
Posted - 2014-08-22 : 09:50:42
|
| I cannot see why you are using a cursor at all. I don't believe it is needed for this problem. (In fact, I don't believe a cursor is ever needed. I'm still looking for a problem that cannot be solved with set-based logic.)What is proc_TOSS_NOTE doing? |
|
|
|
Chris_Kelley
Posting Yak Master
114 Posts |
Posted - 2014-08-23 : 17:28:27
|
| c |
|
|
|
gbritton
Master Smack Fu Yak Hacker
2780 Posts |
Posted - 2014-08-24 : 08:52:23
|
| Cursors should be avoided at all costs. If the toss_note process just does an insert, I'd pull the logic into your new proc which can be entirely set based. |
|
|
|
gbritton
Master Smack Fu Yak Hacker
2780 Posts |
Posted - 2014-08-24 : 08:52:29
|
| Cursors should be avoided at all costs. If the toss_note process just does an insert, I'd pull the logic into your new proc which can be entirely set based. |
|
|
|
gbritton
Master Smack Fu Yak Hacker
2780 Posts |
Posted - 2014-08-24 : 08:52:30
|
| Cursors should be avoided at all costs. If the toss_note process just does an insert, I'd pull the logic into your new proc which can be entirely set based. |
|
|
|
Chris_Kelley
Posting Yak Master
114 Posts |
Posted - 2014-08-24 : 21:34:32
|
| c |
|
|
|
|
|
|
CURSOR w\multiple tables