Hi All

I have a problem with performance on an Axapta 3.0 sp4 installation
While examing the installation on a server I am using for connecting
3rdparty software to Axapta I have found that the mssql client installed is
version 8.00.194 (RTM)
http://www.krell-software.com/mssql-builds.asp

Would this client intallation need to be upgraded to match the SQL server
version Axapta uses
Would it affect performance or should I look elsewhere?

I only have DLL and ressource files installed no client tools (executables)
How can examine which network libraries are in use?

Thanks/Peter

--
Hi! I'm a .signature *virus*!
Copy me into your ~/.signature to me spread!

Peter Lykkegaard wrote:
>
How can examine which network libraries are in use?

This is what I have from netstat (-ano) when my program is active

Local Foreign State PID
--------------------------------------------------------
(...)
<client> 3390 <mssql> 1433 TimeWait 0
<client> 3391 <mssql> 1433 TimeWait 0
<client> 3401 <mssql> 1433 Established 4892
<client> 3402 <mssql> 1433 Established 4892
(...)
--------------------------------------------------------

- Peter

--
Hi! I'm a .signature *virus*!
Copy me into your ~/.signature to me spread!

Hello Peter,

For sqlclient version, since I'm not familar with Dynamic AX, I haven't got
any definite document on whether you should manually update the sqlcilent
version to the latest. For the client-side SQL protocol, if you only use
sql server 2000, the built-in tool (%windir%\system32\cliconfg.exe) can
manage it.

For SQL Server 2005, it add updated protocol components, if you haven't
installed client configuration tool, I'm afraid you may have to check the
registry. the client protocol's regrisy setting are under the following
path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\SNI9.0

the "ProtocolSupported" value represent all the supported protocols and the
"ProtocolOrder" represent those currently enabled protcols in order.

In addition, since this is a dynamix AX awared issue, I would suggest you
also posted in those dynamics AX specific communities:

#Microsoft Dynamics-related communities
http://www.microsoft.com/dynamics/co...eslanding.mspx

#Microsoft Dynamics Forums
http://www.microsoftdynamicsforums.c...ms/default.asp

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

==================================================



This posting is provided "AS IS" with no warranties, and confers no rights.

Steven Cheng[MSFT] wrote:
>
> For sqlclient version, since I'm not familar with Dynamic AX, I
> haven't got any definite document on whether you should manually
> update the sqlcilent version to the latest. For the client-side SQL
> protocol, if you only use sql server 2000, the built-in tool
> (%windir%\system32\cliconfg.exe) can manage it.
>
Ok thanks I'll have a look

> For SQL Server 2005

I am quite sure it's the 2000 version

> In addition, since this is a dynamix AX awared issue, I would suggest
> you also posted in those dynamics AX specific communities:
>
I know I have already posted a similar message in m.p.a
Should have mentioned it though

/me slaps myself

Thanks/Peter