![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I've read that the advantages of sprocs over embedded queries is that the former are compiled once. Does one loose the advantages of stored procedures when one concatentates a lot of strings together and then uses the EXEC function to execute the subsequent query? I'm seeing a lot of this in the stored procedures I'm debugging. Thanks, Siegfried |
#3
| |||
| |||
|
|
I've read that the advantages of sprocs over embedded queries is that the former are compiled once. Does one loose the advantages of stored procedures when one concatentates a lot of strings together and then uses the EXEC function to execute the subsequent query? I'm seeing a lot of this in the stored procedures I'm debugging. Thanks, Siegfried |
#4
| |||
| |||
|
|
I've read that the advantages of sprocs over embedded queries is that the former are compiled once. Does one loose the advantages of stored procedures when one concatentates a lot of strings together and then uses the EXEC function to execute the subsequent query? I'm seeing a lot of this in the stored procedures I'm debugging. Thanks, Siegfried |
#5
| |||
| |||
|
|
I've read that the advantages of sprocs over embedded queries is that the former are compiled once. Does one loose the advantages of stored procedures when one concatentates a lot of strings together and then uses the EXEC function to execute the subsequent query? I'm seeing a lot of this in the stored procedures I'm debugging. Thanks, Siegfried |
#6
| |||
| |||
|
|
I've read that the advantages of sprocs over embedded queries is that the former are compiled once. Does one loose the advantages of stored procedures when one concatentates a lot of strings together and then uses the EXEC function to execute the subsequent query? I'm seeing a lot of this in the stored procedures I'm debugging. Thanks, Siegfried |
#7
| |||
| |||
|
|
I've read that the advantages of sprocs over embedded queries is that the former are compiled once. Does one loose the advantages of stored procedures when one concatentates a lot of strings together and then uses the EXEC function to execute the subsequent query? I'm seeing a lot of this in the stored procedures I'm debugging. Thanks, Siegfried |
#8
| |||
| |||
|
|
I've read that the advantages of sprocs over embedded queries is that the former are compiled once. Does one loose the advantages of stored procedures when one concatentates a lot of strings together and then uses the EXEC function to execute the subsequent query? I'm seeing a lot of this in the stored procedures I'm debugging. Thanks, Siegfried |
#9
| |||
| |||
|
|
I've read that the advantages of sprocs over embedded queries is that the former are compiled once. Does one loose the advantages of stored procedures when one concatentates a lot of strings together and then uses the EXEC function to execute the subsequent query? I'm seeing a lot of this in the stored procedures I'm debugging. Thanks, Siegfried |
#10
| |||
| |||
|
|
I've read that the advantages of sprocs over embedded queries is that the former are compiled once. Does one loose the advantages of stored procedures when one concatentates a lot of strings together and then uses the EXEC function to execute the subsequent query? I'm seeing a lot of this in the stored procedures I'm debugging. Thanks, Siegfried |
![]() |
| Thread Tools | |
| Display Modes | |
| |