Hello,
I need to change for an old db (SQL 2K) the property Accent-sensitive to Accent-insensitive and I don't know how .
If someone has a solution I needs some help please.
Thank you.Example: on a database named Products with the language French
ALTER DATABASE Products
COLLATE French_CI_AI
the CI_AI tells it to be Case Insensitive and Accent Insensitive|||Originally posted by Memnoch1207
Example: on a database named Products with the language French
ALTER DATABASE Products
COLLATE French_CI_AI
the CI_AI tells it to be Case Insensitive and Accent Insensitive
I try but doesn't work .
The script : ALTER DATABASE Products COLLATE French_CI_AI
return : The command(s) completed successfully.
but my select with : WHERE id = 'abcd' and WHERE id = 'abcde' is different .
?!|||Changed default database collation only.
You must alter all tables in you database.
A,Change collation of table columns by EM.
B,Faster would be
1.Generate script for all database by EM to text file without Generate drop existing option.
2.Open this file in notepad
3.Replace collation strings French_CI to French_CS (use your collation)
4.Copy create database part to QA and change database name and run
5.Switch to new database
5.Copy create tables part to QA and run
6.Use DTS wizard to copy data from your old database
7.Copy all remaining code to QA and run
8.Switch your databases by sp_renamedb (old->bak,new->old)
Note that server can use different collation from database. TempDb uses collation of model.
Showing posts with label old. Show all posts
Showing posts with label old. Show all posts
Sunday, March 11, 2012
Accent-insensitive HELP.
Labels:
accent-insensitive,
accent-sensitive,
database,
microsoft,
mysql,
old,
oracle,
property,
server,
sql
Saturday, February 25, 2012
About Sql25K and MDAC libraries
Dear all,
There is a problem which I am concerned about and is that kind of
compatibility own the old libraries, i.e, ado 2.5,2.6.,2.7sp1 within a Sql
Server 2005 framework.
We have a lot of old applications running with 2.6 and using RDO or even
DAO!!!
Does anyone have or is awared of any link related, any map or schema very
representative of all this stuff? Is very tricky try to imagine how manage
myself with such diversity of applications
Thanks in advance and regards,
Enric wrote on Wed, 22 Mar 2006 00:15:27 -0800:
> Dear all,
> There is a problem which I am concerned about and is that kind of
> compatibility own the old libraries, i.e, ado 2.5,2.6.,2.7sp1 within a Sql
> Server 2005 framework.
> We have a lot of old applications running with 2.6 and using RDO or even
> DAO!!!
> Does anyone have or is awared of any link related, any map or schema very
> representative of all this stuff? Is very tricky try to imagine how manage
> myself with such diversity of applications
> Thanks in advance and regards,
I have some VB apps using ADO 2.1 via ODBC that work fine with SQL Server
2005. ADO is an abstraction layer, not a driver library. SQL Server 2005
still supports the older connection methods.
Dan
There is a problem which I am concerned about and is that kind of
compatibility own the old libraries, i.e, ado 2.5,2.6.,2.7sp1 within a Sql
Server 2005 framework.
We have a lot of old applications running with 2.6 and using RDO or even
DAO!!!
Does anyone have or is awared of any link related, any map or schema very
representative of all this stuff? Is very tricky try to imagine how manage
myself with such diversity of applications
Thanks in advance and regards,
Enric wrote on Wed, 22 Mar 2006 00:15:27 -0800:
> Dear all,
> There is a problem which I am concerned about and is that kind of
> compatibility own the old libraries, i.e, ado 2.5,2.6.,2.7sp1 within a Sql
> Server 2005 framework.
> We have a lot of old applications running with 2.6 and using RDO or even
> DAO!!!
> Does anyone have or is awared of any link related, any map or schema very
> representative of all this stuff? Is very tricky try to imagine how manage
> myself with such diversity of applications
> Thanks in advance and regards,
I have some VB apps using ADO 2.1 via ODBC that work fine with SQL Server
2005. ADO is an abstraction layer, not a driver library. SQL Server 2005
still supports the older connection methods.
Dan
About Sql25K and MDAC libraries
Dear all,
There is a problem which I am concerned about and is that kind of
compatibility own the old libraries, i.e, ado 2.5,2.6.,2.7sp1 within a Sql
Server 2005 framework.
We have a lot of old applications running with 2.6 and using RDO or even
DAO!!!
Does anyone have or is awared of any link related, any map or schema very
representative of all this stuff? Is very tricky try to imagine how manage
myself with such diversity of applications
Thanks in advance and regards,Enric wrote on Wed, 22 Mar 2006 00:15:27 -0800:
> Dear all,
> There is a problem which I am concerned about and is that kind of
> compatibility own the old libraries, i.e, ado 2.5,2.6.,2.7sp1 within a Sql
> Server 2005 framework.
> We have a lot of old applications running with 2.6 and using RDO or even
> DAO!!!
> Does anyone have or is awared of any link related, any map or schema very
> representative of all this stuff? Is very tricky try to imagine how manage
> myself with such diversity of applications
> Thanks in advance and regards,
I have some VB apps using ADO 2.1 via ODBC that work fine with SQL Server
2005. ADO is an abstraction layer, not a driver library. SQL Server 2005
still supports the older connection methods.
Dan
There is a problem which I am concerned about and is that kind of
compatibility own the old libraries, i.e, ado 2.5,2.6.,2.7sp1 within a Sql
Server 2005 framework.
We have a lot of old applications running with 2.6 and using RDO or even
DAO!!!
Does anyone have or is awared of any link related, any map or schema very
representative of all this stuff? Is very tricky try to imagine how manage
myself with such diversity of applications
Thanks in advance and regards,Enric wrote on Wed, 22 Mar 2006 00:15:27 -0800:
> Dear all,
> There is a problem which I am concerned about and is that kind of
> compatibility own the old libraries, i.e, ado 2.5,2.6.,2.7sp1 within a Sql
> Server 2005 framework.
> We have a lot of old applications running with 2.6 and using RDO or even
> DAO!!!
> Does anyone have or is awared of any link related, any map or schema very
> representative of all this stuff? Is very tricky try to imagine how manage
> myself with such diversity of applications
> Thanks in advance and regards,
I have some VB apps using ADO 2.1 via ODBC that work fine with SQL Server
2005. ADO is an abstraction layer, not a driver library. SQL Server 2005
still supports the older connection methods.
Dan
About Sql25K and MDAC libraries
Dear all,
There is a problem which I am concerned about and is that kind of
compatibility own the old libraries, i.e, ado 2.5,2.6.,2.7sp1 within a Sql
Server 2005 framework.
We have a lot of old applications running with 2.6 and using RDO or even
DAO!!!
Does anyone have or is awared of any link related, any map or schema very
representative of all this stuff? Is very tricky try to imagine how manage
myself with such diversity of applications
Thanks in advance and regards,Enric wrote on Wed, 22 Mar 2006 00:15:27 -0800:
> Dear all,
> There is a problem which I am concerned about and is that kind of
> compatibility own the old libraries, i.e, ado 2.5,2.6.,2.7sp1 within a Sql
> Server 2005 framework.
> We have a lot of old applications running with 2.6 and using RDO or even
> DAO!!!
> Does anyone have or is awared of any link related, any map or schema very
> representative of all this stuff? Is very tricky try to imagine how manage
> myself with such diversity of applications
> Thanks in advance and regards,
I have some VB apps using ADO 2.1 via ODBC that work fine with SQL Server
2005. ADO is an abstraction layer, not a driver library. SQL Server 2005
still supports the older connection methods.
Dan
There is a problem which I am concerned about and is that kind of
compatibility own the old libraries, i.e, ado 2.5,2.6.,2.7sp1 within a Sql
Server 2005 framework.
We have a lot of old applications running with 2.6 and using RDO or even
DAO!!!
Does anyone have or is awared of any link related, any map or schema very
representative of all this stuff? Is very tricky try to imagine how manage
myself with such diversity of applications
Thanks in advance and regards,Enric wrote on Wed, 22 Mar 2006 00:15:27 -0800:
> Dear all,
> There is a problem which I am concerned about and is that kind of
> compatibility own the old libraries, i.e, ado 2.5,2.6.,2.7sp1 within a Sql
> Server 2005 framework.
> We have a lot of old applications running with 2.6 and using RDO or even
> DAO!!!
> Does anyone have or is awared of any link related, any map or schema very
> representative of all this stuff? Is very tricky try to imagine how manage
> myself with such diversity of applications
> Thanks in advance and regards,
I have some VB apps using ADO 2.1 via ODBC that work fine with SQL Server
2005. ADO is an abstraction layer, not a driver library. SQL Server 2005
still supports the older connection methods.
Dan
Subscribe to:
Posts (Atom)