Sorry I cannot help you further.

Data stored in Sql Server 2005
in a table the Column Consists Data in iscii Format how
Can i Show that data in specifeid Language

The Data was inserted using CDAC iplugin the Language Used is Telugu
Waiting..;
For Reply
Data is visible in this format

Data stored in Sql Server 2005
in a table the Column Consists Data in iscii Format how
Can i Show that data in specifeid Language

The Data was inserted using CDAC iplugin the Language Used is Telugu
Waiting..;
For Reply

This is a very complex process that, depending on the size of your database, could be impossible to do manually. Here’s what needs to be done:

1. Identify all the columns which have incorrect collation values.
2. Identify all objects bound to above columns, including indexes, keys, checks and UDF’s,
3. Script out all of the above object DDL.
4. Drop all of the objects.
5. Update all the columns with the correct collation
6. Recreate all of the dropped objects using the DDL generated in step 3

Fortunately, I’ve written a set of scripts to do all this and have them documented and published here on the SQLAuthority site.

The following page should provide you with everything you need.
http://blog.sqlauthority.com/2009/10/19/sql-server-change-collation-of-database-column-t-sql-script-consolidating-collations-extention-script/

Hope this helps.

‘alter database testCollationChange
collate SQL_Latin1_General_CP1_CI_AS ‘

Is anyother script?

both columns are character date type

Thanks a lot Brian!

If they are string based types, try the following:

SELECT ITEMNMBR
FROM IV00101 i
LEFT JOIN CRMLINKED.CRMDB.dbo.ProductBase p
ON p.productnumber COLLATE SQL_Latin1_General_CP1_CI_AS = i.ITEMNMBR
WHERE p.productnumber IS NULL

i modified the query like this

SELECT ITEMNMBR
FROM IV00101
WHERE
ITEMNMBR NOT IN ( select productnumber from CRMLINKED.CRMDB.dbo.ProductBase where productnumber COLLATE SQL_Latin1_General_CP1_CI_AS )

but still got the error
Cannot resolve the collation conflict between “Modern_Spanish_CI_AI” and “SQL_Latin1_General_CP1_CI_AS” in the equal to operation.

any other ideas please

thanks a lot

but i got this error
Cannot resolve the collation conflict between “Modern_Spanish_CI_AI” and “SQL_Latin1_General_CP1_CI_AS” in the equal to operation.

i even put at the end COLLATE SQL_Latin1_General_CP1_CI_AS

but i still got the same error
it’s not posible to change the collations of the DBs

could you help me please

thanks a lot

Is it possible to set a collation sequence on a schema so all tables within that schema are case-sensitive, whereas rest of database is case-insensitive?

Cheers
Gordon

There are a couple of edits you’ll probably need to make to the individual scripts, for example, the collation you intend to use. The scripts have Latin1_General_CI_AS hard-coded.

Read all the accompanying documentation. Hopefully it will answer any questions you have about how to implement these.

And of course, if you have additional questions, my email is posted in the article.

Here it is… Enjoy.

Brian

http://blog.sqlauthority.com/2009/10/19/sql-server-change-collation-of-database-column-t-sql-script-consolidating-collations-extention-script/

Unfortunately, the documentation is only from my POV, and has NOT been beta tested against the masses.

I am emailing the article to Pinal Dave along with the scripts, but I have no control over when he has the time to review and publish.

For those of you that have urgent needs… you’ve got to realize, your email address is NOT posted, nor is mine. The back-end of Pinal’s blog filters out email address in posts. No way for me to know where to send. So, if time is of the essence, be a little diligent and refer to my posts on March 2nd and September 12th. My email address is obfuscated in the CONVERT() statement. Just copy and paste it in a Q/A window.

Really looking forward to your post. I think it will be great additional for readers for this blog. I will post it with due credit.

Kind Regards,
Pinal

I’m glad you got the issue sorted out. Incidentally, the code I posted above was only to reveal my email address. Nothing fancy, but it gets thru the spam filters, and I didn’t want any screen-scrapers to add me to their spam targets.

For all others, I will see if I can find the time to patch up the code and make it a bit more generic. Then I’ll write it up and pass it on to Pinal for posting, so that people can grab it a little easier. I don’t have a blog, so I’ll drop the scripts here.

I’ve actually managed to fix the problem. Our application has a built in ‘create database’ function which creates a copy of the existing database as a new one, including all the data in the tables. I changed the database collation to the correct one and when I ran the process it created a new database and assigned the default (correct) collation to all the columns.

Thanks for getting back to me though.

Cheers,
James

Thanks for the response. I have tried executing the code you posted but I just get a series of errors;

Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near ‘×’.
Msg 168, Level 15, State 1, Line 1
The floating point value ’427269616e277320656′ is out of the range of computer representation (8 bytes).
Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near ‘×’.
Msg 168, Level 15, State 1, Line 1
The floating point value ’6263696465726e20617420676′ is out of the range of computer representation (8 bytes).

I assume I’m doing something wrong..

Don’t know if this will get through but my handle is james.wishart and the domain is activa.com.au

Cheers,
James

It is correct, that automatic settings discards the comments and move to spam.

If you have any good idea about this subject, I encourage you to write down good small post about the subject and I publish as blog post with due credit to you along with your contact info.

Kind Regards,
Pinal Dave

Also, it seems that whenever I post contact information, the post gets discarded. So….

Please execute the following. The results will be painfully obvious.

SELECT CONVERT(VarChar(20), 0×427269616e277320656d61696c3a)
UNION ALL
SELECT CONVERT(VarChar(30), 0×6263696465726e20617420676d61696c20646f7420636f6d)