Please look into this

create procedure proc_test as

begin

declare @name varchar(100)

set @name="Gopi"

select @name

end

If you execute this SQL Server 2000 through an error like this

Server: Msg 207, Level 16, State 3,...

I can see the only problem is

 set @teste_varchar2 = "valor_fact" use single quotes instead of double quotes

replace your temporary tables with table data type, which is allowed in UDF's

Use User Defined Functions instead of Stored Procedure

try this

select

a.id,a.name,a.tracking_number,a.start_date,

I am totally agree with you..

But with careful validation of User Input at Front End Side and in Stored Procedure we can eliminate this type of vulnerabilities

Basically I like dynamic...

I appreciate the explanation..

I guess you are talking about cons of dynamic sql.. Any way our situation is not this.. we are selecting columns dynamically from a table

I agree that...

Thanks for your quick response..

what are the disadvantages of using dynamic sql in stored procedure over your specified approach ( I really didn't get it properly)

I really like to know the approaches..

which can be used in this situation .

I understand the situation as  Creating the resultset based on user requested columns .

Use dynamic sql in procedure

Yes, Using Output paremeters it should work

try this

SELECT i.ItemNmbr, i.ListPrce,i1.ListPrce

FROM IV00105 AS i left join (SELECT ItemNmbr, ListPrce FROM IV00105 AS i1 WHERE  i1.ItemNmbr like '%Core') AS i1

on i.ItemNmbr=left(i1.ItemNmbr,len(i1.ItemNmbr)-5)

WHERE i.ItemNmbr NOT LIKE '%Core'

try this

SET @queryString = 'SELECT b.employee_no, a.Access_Seq FROM ' +

                               rtrim(convert(char,@dbName)) + '..employee a, ' + rtrim(convert(char,@dbName)) + '..userlog b WHERE a.employee_no = b.employee_no

                               AND b.uname = '''...

Good Catch..

Yes, Case is a function in T-SQL

TRY THIS

DECLARE

CUR CURSOR FOR SELECT FIELD FROM ACTIVE_FIELDS WHERE STATUS