Trying to diagnose an problem, I've ran into that inconsistency.
In SQL Server Profiler, the RPC Starting
event uses the regional settings to write real numbers (example: in Portuguese(Brazil) 14.5 will be expressed as 14,5).
Normally that's not a problem, except where the RPC call is a stored procedure with real number parameters. So what is expected to be expressed as:
exec usp_something 'blabla', 14.5
Is expressed as:
exec usp_something 'blabla', 14,5
Which gives a lot of headaches when you have a long parameter list. Didn't find any clue online how to change that behavior.
Someone knows a way to change that behavior?
Btw: I'm aware that the workaround is to use SP Starting
event instead, which uses '.' for decimal separator.
rpc_starting
events? I suspect this is a bug but, given Profiler/SQL Trace are deprecated, it might not get much attention. – Dan Guzman May 11 '18 at 10:14