Create UDF and use it in your scripts.

@IntDate will be a parameter for this UDF.

SELECT @Year = @IntDate / 1000

SELECT @Day = IntDate - @Year*1000

SELECT @Date = dateadd(yy, @Year,...

It says "Incorect syntax".

So, it is.

SET @myprovstr= 'DRIVER ...

And next time don't expose you passwords to everybody.

Both queries do date comparison.

Just don't apply functions to columns in WHERE clause.

Will you replace some hardware in my home as well?

This site glitches on my place as well.

Read my script again.

If your project not suppose to stay a toy in your sandbox always do performance test before apply any solution.

SELECT TOP 1000000 IDENTITY(int, 1,1) as ID, cast(NULL as varchar(10)) as...

If you really expose everything and nothing left beyond the scope I would suggest to leave everything and try to save your database.

It's easier not to let them in.

Set up a trigger which will test if inserted line(s) are allowed to be in the table and remove those which are not.

What if you query this:

select trn_ext_bat_id, trn_task_code, CONVERT(varbinary(8000), trn_task_code)

Whar about Miss, Dr., Snr., Sir end in the end?

Or just simple Valery, Alex, etc.

SELECT CONVERT(NUMERIC(28, 2), CONVERT(FLOAT, '2.5608655E7'))

Is there only one trn_ext_bat_id value in the table?

Why does you resultset display only one row?

Is it like this:

select @trn_ext_bat_id = trn_ext_bat_id,

@count = count(*)

from o_transfer

where trn_ext_bat_id is null

and substring(trn_task_code,4,2)...

How deep is your knowledge of SQL Server sequrity?

What makes you believe your statement is correct?

Set up proper security model and don't give sa password to anybody.