I'm going to use SQL Server 2014 in memory table with a database which has Arabic_CI_AS collation but when I create in memory table is says oltp does not support this collation.
Is there any way to solve this problem?
Related
I'm migrating tables and views from Oracle to SQL Server using SSMA. I have a number of tables that have columns with SDO_GEOMETRY datatype, SQL Server does not work with that.
How could I map SDO_GEOMETRY to SQL Server? If it's not possible, then what should be done using SSMA?
And is it possible to work out this issue without editing anything in the Oracle database (just using SSMA or SQL Server)?
Oracle use an internal specific Oracle format of geo data that is non standard... Convert it to WKB or WKT and it should works.
Our database has a collation of SQL Latin General CI_AS, we need to change it to SQL Latin General CS_AS.
Is there a way to change the collation without rebuilding the database?
Maybe can we change the collation for specific tables?
I have SQL Server 2014 Express edition installed on a Portuguese Windows 10 computer. I have a database that was created on an US computer. I have changed the collation of the database in SSMS. I examine tables, stored procedures, etc and they all have the default collation of SQL Server (Latin1_General_CI_CA).
When I try to execute a stored procedure in the database, SQL Server barfs up a collation mismatch between Latin1_General_CI_AS and SQL_Latin1_CP1_CI_AS. I have checked everything that I know of and the collation matches.
Really hoping to avoid rewriting all my stored procedures to set the default collation.
Anyone have any ideas?
Thanks in advance.
I state that I'm new to SQL Server.
With my company we are planning to migrate from SQL Server 2008 to SQL Server 2012 and I have this question.
The application which uses SQL Server 2008 was born as a one language application (Italian in this case) but later has been converted to a multi language application that requires UTF-8 encoded data.
So the DB server has been filled with custom "collation" clause on column, query and procedures to avoid data encoding errors.
Now we have configured a SQL Server 2012 instance with all the right collation since the start and I was wondering in how to migrate data between servers.
How can I tell the dbms to dump the data into UFT-8 and omit all those "collation" clauses?
Sorry for my bad English.
I've been working on SQL server 2005 for a few years and i'd never come across collation issues. However i installed SQL 2008 on a virtual machine and tried to sync my 2005 database with the new 2008 server using Redgate SQL compare. It failed complaing about the collation on the 2 servers being different.
After a quick bit of research i discovered my 2005 is using Latin1_General_CI_AS and the new 2008 installation is using SQL_Latin1_General_CP1_CI_AS.
Why is 2008 using something different to 2005? Both times i've just done a default install. Secondly what should i do to get them the same, which collation is the correct one?
I do not know what criteria is used for the MS SQL Server installer to select default collation.
Collation of a server does not have to be the same as the collation of a database on that server. Collation of a database does not have to be the same as the collation of table columns in the database.
You can set the collation of the database when you create one. Default it will get the same collation as the server.
Here is a post about how you can change the collation of a database including changing the collation of columns.
Changing SQL Server Database sorting
with a reference to here http://support.microsoft.com/kb/325335.
Here is a starting point if you need to change the default collation of a server
http://msdn.microsoft.com/en-us/library/ms179254.aspx.
I do not know what is necessary for Redgate SQL Compare, but I guess it only needs the database collation to be the same. So if you are replicating a db to a new server you probably only need to create the new db with the same collation as the one you already have and leave the default collation of the server as is.