Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved Advice related to character encoding - CharSet

  1. New
  2. Advice
0
Votes
Undo
  1. Ramendra Singh
    Ramendra Singh
  2. PowerBuilder
  3. Tuesday, 10 December 2024 02:53 AM UTC

Hi Gurus,

We are migrating our PowerBuilder Apps from Sybase ASE to SQL Server and we noticed that in Sybase, we have CharSet="iso_1" explicitly set as a DBParam.

Our new SQL Server is now has character encoding to "SQL_Latin1_General_CP1_CS_AS" which is slightly different to Sybase "iso_1" 

As per CharSet function help documents, it talk about applicable to Sybase products only 

https://docs.appeon.com/pb2019/connection_reference/ch01s01.html#CharSet

Applies to

ASE, SYC SAP Adaptive Server Enterprise

DIR SAP DirectConnect

I just wanted to check if this parameter is applicable for SQL Server or can be ignored.

Thanks

Ramendra 

 

 

 

  1. Migration
  2. SQL Server
powerbuilder 7.0
Powerbuilder 2022 Themes
Responses (1)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 10 December 2024 03:16 AM UTC
  2. PowerBuilder
  3. # 1

Hi Ramendra ;

  This is only for ASE ...

https://docs.appeon.com/pb2022/connection_reference/CharSet.html

HTH 

Regards ... Chris 

Comment
Ramendra Singh
  1. Ramendra Singh
  2. Tuesday, 10 December 2024 03:29 AM UTC
Thank you Chris for your prompt response.



Is there any equivalent for SQL Server or how PowerBuilder can explicitly supply character encoding for SQL Server.

  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 10 December 2024 13:03 PM UTC
SS 2019 & higher by default uses UTF-8 for all Char & VarChar columns and UTF-16 for all NChar & NVarChar column data. So unlike Unix based DBMS like ASE, character encoding is much more straightforward.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.