Collation setup for SQLServer2000 Standard Edition

After installing sp1 on my Windows 2003 Server I was able to install SQLServer2000, but, during installation I couldn't set up collation options for SQLServer.

I heve seen many screenshots where they say after asked for instance name I should be asked for collation setup options but I can't see them.

I don't know what should I do because my ERP needs to have the SQL_Latin1_General_CP1_C1_AS setup. Can I change this after initial installation?

Thanks in advance...

Quote:

Originally Posted by Marisol

After installing sp1 on my Windows 2003 Server I was able to install SQLServer2000, but, during installation I couldn't set up collation options for SQLServer.

I heve seen many screenshots where they say after asked for instance name I should be asked for collation setup options but I can't see them.

I don't know what should I do because my ERP needs to have the SQL_Latin1_General_CP1_C1_AS setup. Can I change this after initial installation?

Thanks in advance...

If you want to change the Server Collation, please start the installation in below manner (replacing desired Collation name). All The Best !!!

start /wait setup.exe /qb INSTANCENAME=MSSQLSERVER REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=test SQLCOLLATION=Latin1_General_CI_AI

Collation problem (please help)

Hi,

when I install SQL Server it uses a SQL collation (SQL_Latin1_General_CP1_CI_AS), and i created a form haveing Arabic field names and every thing saved on my DataBase, when i call this field to the html page its look fine and visitor can read it , the problem when the clintes (visitors) fill this form and submit it, I can't read the information enterd in the text fields its shown like this (?).

can any one help

YOu will have to insert the values indicating that unicode is inserted. If you are composing your own insert statements, make sure you are using something like N'HereisUnicode' whereas the prefacing N indicated the Unicode character. Unicode data can be stored in unicode data types like Nvarchar etc. If you are no composing your statements on the fly and do parametrized queries (preferable) you should be aware of using the appropiate SQL unicode datatypes (mentioned above)

Jens K. Suessmeyer

http://www.sqlserver2005.de
|||

I'll try that,

thank you alot.