SQL Server Home
Microsoft SQL Server Management Studio doesn't get OS regional Setting
5/26/2009 7:12:06 AM
Primary Feedback Item:
User(s) can reproduce this bug
When Microsoft SQL Server Management Studio start
numeric decimal separator from "Regional setting",
and apply it to Float and Money data only.
For Decimal numeric result output still fixed to English separator.
This is a big issue when copy and paste results into a Excel sheet!!!!
Excel it is buggy too because it doesn't get regional money decimal setting!!!
SQL Server 2008 SP1
Tools (SSMS, Agent, Profiler, etc.)
Windows XP SP2 Professional
Operating System Language
Steps to Reproduce
open "Control Panel" > "Regional setting"
set Numeric decimal separator to "?"
set Money decimal separator to "!"
open Microsoft SQL Server Management Studio
SELECT CAST(1.5123 AS FLOAT)
, CAST(1.5123 AS DECIMAL(9,4))
, CAST(1.5123 AS MONEY)
1!5123 is not good for Excel !!!!!
to post a comment.
Please enter a comment.
on 9/27/2011 at 8:15 PM
Has this been resolved yet? I set my decimal symbol to '*', then I ran the scripts:
select cast('12.34' as float)
declare @flt float
set @flt = 12.34
select convert(varchar, @flt)
I was expecting both results to be 12*34, but only the first script got the expected result, the second one still got 12.34.
This issue has become quite annoying..
on 5/12/2011 at 5:08 AM
This is a followup for issue 317548 (Incorrect decimal setting) you previously reported.
We wanted to update that the issue is reproducible as generic .net CLR issue and is being tracked with connect ID 636074. This issue will be marked as duplicate (info from this issue has been added to 636074).
on 10/12/2010 at 8:24 AM
on 11/27/2009 at 5:38 AM
When I run this (Management Studio SS2008):
SELECT CAST(5 AS NUMERIC(5,2)) / CAST(2 AS NUMERIC(5,2))
SELECT 5.0 / 2.0
SELECT CAST(5 AS float)/ CAST(2 AS float)
I get this:
When I try to copy my results to Excel (decimal datatype) I ALWAYS have to edit de decimal separator.
My regional settings: Spanish-Spain
on 6/25/2009 at 6:54 AM
Hello Fabio Lunardon,
Thank you for reporting this problem. I have marked this bug for consideration for a future release of SQL Server. We will update this space as we make progress on this issue.
to post a workaround.
Please enter a workaround.
© 2013 Microsoft