Re: MDX through OPENQUERY and Linked server. Number Format.

#1

Hi, Vladislav

Both SQL Servers running localsystem account.
How can I check decimal point setting for localsystem?
What regestry key is responsible for decimal point setting.

Thanks,
Vladimir Chtepa

"Vladislav Beliaev" <vbeliaev (AT) mail (DOT) ru> schrieb im Newsbeitrag
news:8fdd9436.0502160426.7d895549 (AT) posting (DOT) google.com...

Quote:

"Vladimir Chtepa" <chtepa (AT) t-online (DOT) de> wrote

Hi,

I've some problem in W2K English + SQL2000 environment
I've discover that ODBO driver used to implement Linked Server
functionality take decimal point settings from the registry
But registry have individual decimal settings for every W2K user
You must verify settings for account on which SQL2000 run
Restart SQL2000 and AS after changing decimal point settings

Hi,
I have accounted a problem by deploing of my solution on Germany Version
of
SQL Server, where the AS is used as Linked Server at MS SQL.

There is development server (Win2K3 German + MSSQL German). Decimal
point is
represented as expected with '.' in the MDX query result .
On the production server (Win2K3 German + MSSQL German) the decimal
point is
represented with ',' and T-SQL is helplessly to parse/cast it to numeric
type.

I have checked that SQL + AS settings till last regestry key are equial
on
both servers. The locale setting of Windows are also equial on both
servers.

What setting/configuration option can change this behaviour?

Thanks,
Vladimir Chtepa

#2

Vladimir Chtepa wrote:

Quote:

What regestry key is responsible for decimal point setting.

HKEY_USERS\.DEFAULT\Control Panel\International

Look onto right side

regards

frank
--
www.xax.de

#3

unfortunately both boxes have the same registry settings under
HKEY_USERS\.DEFAULT\Control Panel\International.
I have tested yet another 2 production servers (Windows Server 2003 DE + SQL
Server 2000 Std. DE). With happiness I have discovered that both have the
same behaviour as my development server. But I have no mind what to do with
production server that have problem (',' as decimal separator in result of
MDX-Queries through Linked Server)

Thanks,
Vladimir Chtepa

"Frank Matthiesen" <fm (AT) xax (DOT) de> schrieb im Newsbeitrag
news:37h7q0F5d1gkeU1 (AT) individual (DOT) net...

Quote:

Vladimir Chtepa wrote:

What regestry key is responsible for decimal point setting.

HKEY_USERS\.DEFAULT\Control Panel\International

Look onto right side

regards

frank
--
www.xax.de

#4

I can't exactly remember what I've done to resolve this problem.
But first of all AS must return point as decimal separator
Please test AS on server for separator

"Vladimir Chtepa" <vc.clean_this (AT) diacom-systemhaus (DOT) clean_this.de> wrote

Quote:

unfortunately both boxes have the same registry settings under
HKEY_USERS\.DEFAULT\Control Panel\International.
I have tested yet another 2 production servers (Windows Server 2003 DE + SQL
Server 2000 Std. DE). With happiness I have discovered that both have the
same behaviour as my development server. But I have no mind what to do with
production server that have problem (',' as decimal separator in result of
MDX-Queries through Linked Server)

Thanks,
Vladimir Chtepa

"Frank Matthiesen" <fm (AT) xax (DOT) de> schrieb im Newsbeitrag
news:37h7q0F5d1gkeU1 (AT) individual (DOT) net...
Vladimir Chtepa wrote:

What regestry key is responsible for decimal point setting.

HKEY_USERS\.DEFAULT\Control Panel\International

Look onto right side

regards

frank
--
www.xax.de

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: MDX through OPENQUERY and Linked server. Number Format.

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap

Re: MDX through OPENQUERY and Linked server. Number Format. - 02-16-2005 , 08:54 AM

Re: MDX through OPENQUERY and Linked server. Number Format. - 02-16-2005 , 09:44 AM

Re: MDX through OPENQUERY and Linked server. Number Format. - 02-16-2005 , 03:15 PM

Re: MDX through OPENQUERY and Linked server. Number Format. - 02-16-2005 , 10:28 PM