Home Dashboard Directory Help
Search

Microsoft SQL Server Management Studio doesn't get OS regional Setting by Fabio Lunardon


Status: 

Resolved
 as External Help for as External


18
0
Sign in
to vote
Type: Bug
ID: 458416
Opened: 5/26/2009 7:12:06 AM
Access Restriction: Public
Primary Feedback Item: 636074
0
Workaround(s)
view
11
User(s) can reproduce this bug

Description

When Microsoft SQL Server Management Studio start
it get
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!!!

Details
Sign in to post a comment.
Posted by wEneedTotaLk 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..
Posted by Microsoft on 5/12/2011 at 5:08 AM
Hi Fabio,

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).

thank you

Seshagiri
PM, SSMS
Posted by abatishchev on 10/12/2010 at 8:24 AM
No news?
Posted by milho1 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:
2.50000000
2.500000
2,5

When I try to copy my results to Excel (decimal datatype) I ALWAYS have to edit de decimal separator.

My regional settings: Spanish-Spain
Posted by Microsoft 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.

Thanks
-Karthik
Sign in to post a workaround.