How can we check the language by which functions, stored-procedures, and triggers are written in

Hi, all here,

Could please any experts here give me any guidance in what way can we check in what language (T-SQL or CLR language?) the user defined database engine objects :functions, stored-procedures and triggers are written?

Thanks a lot in advance for any guidance and advices for that.

With best regards,

Yours sincerely,

Sys.objects provides that information

Have a look at this page in BOL ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/f8d6163a-2474-410c-a794-997639f31b3b.htm

|||

Hi, Simon,

Thanks a lot.

With best regards,

Yours sincerely

How can we check the language by which functions, stored-procedures, and triggers are writte

Hi, all here,

Could please any experts here give me any guidance in what way can we check in what language (T-SQL or CLR language?) the user defined database engine objects :functions, stored-procedures and triggers are written?

Thanks a lot in advance for any guidance and advices for that.

With best regards,

Yours sincerely,

Sys.objects provides that information

Have a look at this page in BOL ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/f8d6163a-2474-410c-a794-997639f31b3b.htm

|||

Hi, Simon,

Thanks a lot.

With best regards,

Yours sincerely

how can i use comma like a decimal separator?

"update product set price='1,99' where cod='001'"

I need COMMA... not DOT

In oracle i use "alter session set language='Brazil'"... but... in SQL SERVER?

i need help...

You would have to change your Windows collation. That is where the translation is occuring.

how can i use comma like a decimal separator?

"update product set price='1,99' where cod='001'"

I need COMMA... not DOT

In oracle i use "alter session set language='Brazil'"... but... in SQL SERVER?

i need help...

hi,

SQL Server just uses "dot" as decimal separator... you have to replace your strings removing the thousands separator, if present, and modify the decimal separator as indicated..

or just use a Command object instead of dynamic SQL, so that the command parameter's value(s) will be set accordingly to your locale settings and you do not have to deal with that kind of troubles... more, you completely bypass lots of SQL injection troubles as, for instance, a datetime parameter can not accept something like

param.Value = '20060101'''; DELETE FROM other_table'

or the like... and you can better check each parameter for validity..

regards

How can i use comma like a decimal separator?

"update product set price='1,99' where cod='001'"

I need COMMA... not DOT

In oracle i use "alter session set language='Brazil'"... but... in SQL SERVER?

You're in the wrong place. Go here: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1

-Jamie