>>>You can use dynamic sql
DECLARE @sql nvarchar(4000)
>>>SET @sql = 'SELECT * FROM ' + @Table + 'WHERE ...'
>>>EXECUTE (@sql)
>>>
>>
>>Sergey,
>>
>>I was wondering, from your experience, is there much gain in speed if you put the dynamic SQL in a stored procedure, versus, sending this SQL statement to SQL Server through SPT (VFP)?
>
>Dmitry,
>IMHO if you have full control on what's passed as parameters (or control them before processing for malicious code) speed wouldn't be a matter. IOW if you have full trust to the sender of those parameters then no problem, else ...:)
>Cetin
Cetin,
I have not even thought of malicious code. But I don't see it as a problem in my case. As I am making baby steps in converting a very big application from VFP database to SQL Server, I often times have a question whether stored procedure is better. And since I don't know much on how to write stored procedures, I choose to write the code in VFP and use SPT.
Thank you for your input.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
