AlwaysOn & Contained Databases Collation Conflict

Here is my situation.
I have setup an alwaysOn availability group which is working fine.
In this AlwaysOn availability group I have converted the Adventureworks database to a contained database. I also added a Contained User.
Connecting to the secondary "Contained" database was no problem.
But here is my problem, when expanding the tables I received the following errormessage:"Cannot resolve collation conflict between "Latin1_General_CI_AS" and "Latin1_General_100_CI_AS_KS_WS_SC" in add operator occurring in SELECT statement
column 3."
Doing this action on the primary is no problem. Executing a select statement against the secondary is also no problem and returns a result.
After some trial and error, I’ve seem to fixed the issue by doing a failover to all my secondary databases.
After, expanding the tables to the primary & secondary worked.
Does anybody have an idea why this happened, and am I the only one experiencing this issue?
Thanks, Bram

Hi
Please refer to the link below:
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/02/26/sql-server-2012-partially-contained-databases-part-2-collation.aspx

Similar Messages

Collation conflict with Crystal Reports & a Primavera database

I'm new to Crystal Reports 2008 SP3; however, I'm ready to toss it out in relation to Primavera (version 7.0) data connectivity on my SQL Server - Windows 2008 R2 Standard (64-bit).
I have finally been able to establish a connection to the database (JDBC) - after struggling to get the right driver [sqljdbc.jar] on our SQL Server.
Now, I'm getting getting an error message relating to a COLLATION SETTING conflict:
'Failed to retrieve data from the database. Details: SQL Exception: [SQL State:] S0009 [Error Message:] Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AI" in the INTERSECT operation. [Database Vendor Code: 468]'
- Primavera version 7.0 default collation is SQL_Latin1_General_CP1_CI_AS
- I have searched the web for hints to resolving this error. Everything is pointing to the collation setting needing to be changed on the SQL Server.
__ Now, I'm checking on how to verify and change the collation setting on the SQL Server.
However, I'm suspecting that there is going to be another error around-the-corner.
It was my expectation & understanding that linking to various databases was a strong point for Crystal Reports. I have been working with another IT peer that is successfully using Crystal Reports for Remedy (HelpDesk application).
Has anyone experienced this situation? (any help is greatly appreciated)
Is there something (else) that is real obvious that I'm missing that would be ?

Don - Thanks for the feedback
I'm using JDBC bacuse I couldn't figure out how to use ODBC. The JDBC driver that I'm trying to use is: sqljdbc.jar which I downloaded last week (MS SQL Service JDBC Driver 3.0 ... version 3.0.1301.101 ... date published 04/20/2010). This driver (sqljdbc.jar) was added to the Classpath in CRConfig.xml.
I did install Fix Pack 3.3, my laptop has Windows XP Professional 32-bit - I have JAVA version 6 Update 14 as the enable version on my computer.
I don't understand when you say "use the MS SQL Server Native 10 as your driver" - I cannot find that by itself on the MS Download site. I keep getting 'MS SQL Server 2008 Feature Pack August 2008' to be downloaded. I'm guessing that this driver should already be loaded; however, I need to know the specific name to add to the Classpath in CRConfig.xml.
__ I found an article [SQL Server Natice Client 10.0 ODBC Driver] that stated the ODBC driver is contained in the file sqlncli10.dll
-- I searched my local harddrive (C:) and it is not found
-- Would this be stored on SQL server itself?
-- I'm guessing that I need to download the 'MS SQL Server 2008 Feature Pack' onto my lapttop
Still grabbing at the air...

Project Server (SharePoint) - Database Collation question.

Hi,
I have been looking at the performance of our SharePoint database server and one of its uses is Project Server.
Our databases are set as follows
Project Server Databases (Latin1_General_CI_AS)
SharePoint Server Content Databases (Latin1_General_CI_AS_KS_WS)
TempDB (Latin1_General_CI_AS)
It seems that the Project Server databases should be (SQL_Latin1General_CP1_CI_AS):
https://technet.microsoft.com/en-us/library/ff800813(v=office.14).aspx
e.g.
Database
Collation
Project Server Archive
SQL_Latin1_General_CP1_CI_AS
Project Server Draft
SQL_Latin1_General_CP1_CI_AS
Project Server Published
SQL_Latin1_General_CP1_CI_AS
Project Server Reporting
SQL_Latin1_General_CP1_CI_AS
SharePoint Server Content
Latin1_General_CI_AS_KS_WS
I may be worrying unnecessarily but my understanding was that the tempdb should be the same collation as the user databases (where possible). With the SharePoint content and the Project Server databases on the same instance this is not possible.
Should I...
1. Not worry about it (the performance impact is negligable).
2. Create seperate instances so that the TempDB can match the user databases (I am worried that the overhead of an extra instance will be more than the overhead of different collations).
3. Implement Contained/Partially contained databases (new possible option)
4. Something else?
Also how bad is it that the Project server databases are Latin1_General_CI_AS rather than SQL_Latin1General_CP1_CI_AS.
Thanks in advance
Shaun

Hi Prasanna,
thank you for taking the time to respond.
From the link - I read this as Microsoft insisting that you use Latin1_General_CI_AS_KS_WS for the SharePoint content databases and recommending it for the system databases including TempDB?
Our TempDB is not the same collation as the SharePoint content databases but the same as the Project Server databases. Which brings me back to my original questions.
From the Technet article:
The following TechNet Article talks about the SQL Server collation for the SharePoint databases
http://technet.microsoft.com/en-us/library/cc288970.aspx#section1
“The SQL Server collation must be configured for case-insensitive. The SQL Server database collation must be configured for case-insensitive, accent-sensitive, Kana-sensitive, and width-sensitive. This is to
ensure file name uniqueness consistent with the Windows operating system.”
However, we do not support changing the default collation (Latin1_General_CI_AS_KS_WS) for SharePoint databases to any other collations (CI, AS, KS, WS).
We support any CI collation for the SQL instance (for master, tempdb databases). However we
recommend using Latin1_General_CI_AS_KS_WS as the instance default collation (master, tempdb databases).

Problem : Cannot resolve the collation conflict between ...

Hi
I want select a column from another database base on my current field on current database.
here is my query :
select ms.ServiceID, ms.ServiceName, ms.CoefficientFixedService,
(select Services_Name from MpAdmisson..IAServices_Table where Services_DepartmentID=24 and Services_Name=ms.ServiceName) as N'MpServiceName'
from MedicalServices ms
join MedicalCategories mc on ms.MedicalCategorizationID=mc.MedicalCategorizationID
join Zones z on mc.ZoneID=z.ZoneID
where z.ZoneID=24
but I'm facing this error :
Cannot resolve the collation conflict between "Persian_100_CI_AI" and "Arabic_CI_AS" in the equal to operation.
Also i changed collation of "MpAdmisson" db to "Persian_100_CI_AI" and even restart msSqlServer service, but i'm facing the same error!
where is my problem and how to solve it ?
thanks in advance
http://www.codeproject.com/KB/codegen/DatabaseHelper.aspx

although you changed the collation of the database it does not mean that all the objects changed their collation too automatically.
So far you are correct.
The change is only done when you change the data within the objects, thus recreating the table and moving data in / out or touching each and every value with doing something on the values themselves (the following will not work UPDATE (..) SET ServiceName
= ServiceName, the optimizer is smart enough too see that as a noop).
However, this is flat wrong. This is the story: each character column in a database has a collation tied to it. When you change the collation of a database, you change 1) the collation of the columns in the system tables. 2) The default collation. To change
the collation on the individual columns, you need to alter the column:
ALTER TABLE IAServices_Table
ALTER COLUMN Services_Name <current data type> COLLATE Persian_100_CI_AI [NOT] NULL
Unfortunately, this only works if the column is not indexed and has no constraints tied to it. Any indexes have to be dropped and recreated after the ALTER statement. If the column is a key column and there are referencing foreign keys, they also have to
be dropped and recreated. Thus, this is quite a far-reaching operation. And it may not stop there - with some amount of bad luck, constraints may fail with the new collation.
For this reason, this workaround suggested by Jens, may be your only option in the short term:
If you cannot do this currently, you can still do the following and collate on a per query basis:
select ms.ServiceID, ms.ServiceName, ms.CoefficientFixedService,
(select Services_Name from MpAdmisson..IAServices_Table where Services_DepartmentID=24 and Services_Name=ms.ServiceName COLLATE Persian_100_AS_CI) as N'MpServiceName'
from MedicalServices ms
And this part of Jens's post is correct. To note though is that use of the COLLATE clause voids any index on ServiceName. (Since this index is sorted according the rules of Arabic, and not the rules of Farsi.)
Erland Sommarskog, SQL Server MVP, [email protected]

Collation conflict

Ok, Im doing a query and its all within the same database, same server etc. Looking at the database properties, the collation is set to Latin1_General_BIN, as are the individual tables. So now why would I get an error such as this?
Cannot resolve the collation conflict between "Latin1_General_BIN" and "SQL_Latin1_General_CP1_CI_AS"

Can I update the collation for a individual column?
Yes, ALTER TABLE works, but you need to drop and reapply constraints, defaults and indexes.
However, there is all reason to do it. The COLLATE clause works from a functional point of view, but for performance it can be a disaster.
Erland Sommarskog, SQL Server MVP, [email protected]

Collation conflict error OVGT table

Hi Guys,
I get a collation conflict error as above. Server instance and company databases are now set to same collation "latin1_general_CP1_CI_AS" but still error appears.
Before that company database was on "CP850" setting.
Any ideas to resolve this?
Is there a query I can run to identify tables that have a different collation to database?
Regards

Use
select * from INFORMATION_SCHEMA.tables
select * from INFORMATION_SCHEMA.columns
Petr

Database Collation Conversion

Hi Guru's,
I am trying to copy Production to a new Test server. Production is 32-bit SQL 2000 the new Test Server is x64 bit and SQL 2005.
The problem I face is with the database Collation. Production database is SQL_Latin1_General_CP850_BIN and I'm trying to get it to SQL_Latin1_General_CP850_BIN2 before attaching it to SQL 2005 on the new Test server. I used INSTCOLL.EXE as advised in OSS 600027 and recieved the following message :
Trying to connect...
Connected to <<SERVERNAME>>
Executing conversion of database <<SID>>
Database <<SID>> has been converted to collation SQL_Latin1_General_CP850_BIN2.
However, select databasepropertyex('<<SID>>', 'collation') still returns SQL_Latin1_General_CP850_BIN
The 'server collation' is SQL_Latin1_General_CP850_BIN. Would this affect how the INSTCOLL.EXE would work?
I tried attaching the database to SQL 2005 as SQL_Latin1_General_CP850_BIN and converting it from there and got this message :
Trying to connect...
Connected to <<SERVERNAME>>
This program will only run against SQL Server 2000 newer or equal to version 8.00.780.
Your server is 9.0.3175
You must install SQL 2000, SP3 and the Unicode Hotfix (QFE).
NOTHING DONE!
Can someone please suggest another way to get the SQL 2000 database to BIN2? Or perhaps offer a suggestion to where I'm going wrong with the conversion?
Thanks,
Kye

Hi,
The permitted collations for SQL Server 2000 are as follows:
o SQL_Latin1_General_CP850_BIN (BIN) and
o SQL_Latin1_General_CP850_BIN2 (BIN2).
Only the following 3 combinations are supported by SAP:
.SAP-Basis................
.SQL.Server....
.<SAP.DATABASE>.
.non-Unicode.and.non-Java.
.BIN...........
.BIN............
.non-Unicode.and.non-Java.
.BIN2..........
.BIN2...........
.Unicode.or.Java..........
.BIN2..........
.BIN2...........
The same collation must always be installed for the SQL Server and the
database.
For a non-Unicode system that does not contain any Java components, you can
select both BIN and BIN2. With a Unicode system or a system that contains
Java components, you must select BIN2 as the collation for the server and
database.
For more details refer SAP Note : 505906.
Regards,
Nikunj

Contained Database Users are now available in Azure SQL Database Update preview

Contained Database Users should be of particular help for people migrating to Azure SQL Database. At the moment, this is a preview release but you can start testing. Here is the announcement of the
preview with links to more information.
New SQL Database public preview with new Standard-tier performance level
Previously announced in November 2014 and now available for customers to try, the
new
public preview of SQL Database improves the compatibility of SQL Server applications for Azure SQL Database. Details of this preview are available on the
SQL
Database documentation webpage, including the following key enhancements: easier management of large databases to support heavier workloads with parallel queries
and online indexing, support for programmability functions like CLR and XML index to support more robust application design, improved monitoring and troubleshooting with XEvents and 100 new Dynamic Management Views (DMV), and more performance in the Premium
tier.
To try this preview, please sign up via the Preview
features webpage. Only SQL Database servers with a mix of one or more Basic, Standard, or Premium (not Web or Business) databases are compatible and eligible to
upgrade to the preview. Please note that any move of an existing Basic, Standard, or Premium database into this preview is irreversible; we recommend that you create a database copy or leverage test databases on any server enrolled in this preview.
A new Standard-tier performance level, S3, is also available in this preview which gives you more pricing flexibility between Standard and Premium. S3 will deliver 100 Database Throughput Units (DTU) and all the features available in the Standard tier. Please
note that S3 will appear on your bill as a multiple of S2 until further notice.
For more information, please visit the SQL
Database webpage and the
Microsoft
Azure Blog. For a comprehensive look at pricing, please visit the
SQL
Database pricing webpage.
Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

Hello Rick
That is great, one thing I'd like to ask, does it support SSMS,SSDT?
No sign of that yet, that I’ve seen.....
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

After creating a contained database, getting a login failure error while trying to connect to it.

After creating a contained database and a user with passowrd under the same database, I tried connecting to the contained database. I entered the server name, login credentials and went to the connection properties tab to select the contained database using
<browse server> option under "connect to database". Here I get the login failure error.
TITLE: Browse Server for Database
Failed to connect to server <servername>\<login>. (Microsoft.SqlServer.ConnectionInfo)
But when I manually enter the Database name instead of selecting from the <browse server> option the connection gets through.
Is this a Bug ? Has anyone else faced this error?

Hello,
Is this a Bug ? Has anyone else faced this error?
It's not a bug, it's working as intended. Contained users don't have instance level permissions and cannot "login" to the instance (which is what the "browse" button is attempting). In order for it to work, the database name must be in the connection string
(which with the browse button, it will not be).
Welcome to contained users, they aren't for everyone.
Sean Gallardy | Blog | Microsoft Certified Master

Error collation conflict

I keep getting the following error with this statement
Msg 468, Level 16, State 9, Line 6
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
Statement :
SELECT Clients.biz_name,Clients.ID,Employers.Name,Employers.RefId
FROM ClientBook.dbo.Clients
JOIN za_FinCloud.dbo.Employers
ON Clients.biz_name=Employers.Name
How do I correct this ?

E.g.
SELECT Clients.biz_name ,
Clients.ID ,
Employers.Name ,
Employers.RefId
FROM ClientBook.dbo.Clients
JOIN za_FinCloud.dbo.Employers ON Clients.biz_name = Employers.Name COLLATE SQL_Latin1_General_CP1_CI_AS;
But the question is: Why do you use different collations?

ORA-16025: parameter LOG_ARCHIVE_DEST_2 contains repeated or conflicting at

Dear all,
10.2.0.2 on linux
We are getting the below error in alert log and synchronization stopped
ORA-00922: missing or invalid option
Tue Oct 11 20:40:41 2011
PRMX: Alter session failed: ORA-02097: parameter cannot be modified because specified value is invalid
ORA-16025: parameter LOG_ARCHIVE_DEST_2 contains repeated or conflicting attributes
ORA-16154: suspect attribute: LGWR
ORA-00922: missing or invalid option
Tue Oct 11 20:40:41 2011
Errors in file /u01/PROD/db/tech_st/10.2.0/admin/PROD_dbprod/bdump/prod_j000_23657.trc:
ORA-16025: parameter LOG_ARCHIVE_DEST_2 contains repeated or conflicting attributes
ORA-16154: suspect attribute: LGWR
ORA-00922: missing or invalid option
Tue Oct 11 20:40:41 2011
PRMX: Alter session failed: ORA-02097: parameter cannot be modified because specified value is invalid
ORA-16025: parameter LOG_ARCHIVE_DEST_2 contains repeated or conflicting attributes
ORA-16154: suspect attribute: LGWR
ORA-00922: missing or invalid optionparameters :
SQL> show parameter log
NAME                                 TYPE        VALUE
audit_syslog_level                   string
db_create_online_log_dest_1          string
db_create_online_log_dest_2          string
db_create_online_log_dest_3          string
db_create_online_log_dest_4          string
db_create_online_log_dest_5          string
log_archive_config                   string      DG_CONFIG=(PROD,PROD_STDBY)
log_archive_dest                     string
log_archive_dest_1                   string      LOCATION=/u01/PROD/db/Archive
                                                 MANDATORY
log_archive_dest_10                  string
NAME                                 TYPE        VALUE
log_archive_dest_2                   string      SERVICE=PROD_STDBY LGWR ASYNC
                                                 VALID_FOR=(ONLINE_LOGFILES,PRI
                                                 MARY_ROLE) REOPEN=15 NET_TIMEO
                                                 UT=30 DB_UNIQUE_NAME=PROD_STDB
                                                 Y
log_archive_dest_3                   string
log_archive_dest_4                   string
log_archive_dest_5                   string
log_archive_dest_6                   string
log_archive_dest_7                   string
log_archive_dest_8                   string
NAME                                 TYPE        VALUE
log_archive_dest_9                   string
log_archive_dest_state_1             string      enable
log_archive_dest_state_10            string      enable
log_archive_dest_state_2             string      enable
log_archive_dest_state_3             string      enable
log_archive_dest_state_4             string      enable
log_archive_dest_state_5             string      enable
log_archive_dest_state_6             string      enable
log_archive_dest_state_7             string      enable
log_archive_dest_state_8             string      enable
log_archive_dest_state_9             string      enable
NAME                                 TYPE        VALUE
log_archive_duplex_dest              string
log_archive_format                   string      %t_%s_%r.dbf
log_archive_local_first              boolean     TRUE
log_archive_max_processes            integer     2
log_archive_min_succeed_dest         integer     1
log_archive_start                    boolean     FALSE
log_archive_trace                    integer     0
log_buffer                           integer     15276032
log_checkpoint_interval              integer     100000
log_checkpoint_timeout               integer     1200
log_checkpoints_to_alert             boolean     TRUE
NAME                                 TYPE        VALUE
log_file_name_convert                string
logmnr_max_persistent_sessions       integer     1
remote_login_passwordfile            string      EXCLUSIVEAny idea what am missing ?
Kai

KaiS wrote:
Dear all,
10.2.0.2 on linux
We are getting the below error in alert log and synchronization stopped
ORA-00922: missing or invalid option
Tue Oct 11 20:40:41 2011
PRMX: Alter session failed: ORA-02097: parameter cannot be modified because specified value is invalid
ORA-16025: parameter LOG_ARCHIVE_DEST_2 contains repeated or conflicting attributes
SQL> show parameter log
log_archive_dest_2                   string      SERVICE=PROD_STDBY LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRI
MARY_ROLE) REOPEN=15 NET_TIMEO
UT=30 DB_UNIQUE_NAME=PROD_STDB
YAny idea what am missing ?
KaiHi,
Try change the log_archive_dest_2
SQL > alter system set log_archive_dest_2 = 'SERVICE="PROD_STDBY", LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PROD_STDBY';Cheers

Which user for a contained database - SQL Server 2012

Hi,
if I've a contained db and I need to create an user for this db in order to porting this contained database to different servers inside the same domain, which type of user do I need to create?
For this user I don't want to apply any further configurations.
Any suggests to me, please?

That still doesn't parse to me... Lets break it down:
"...for the contained db to port to a server to another server in the same domain..."
I assume you mean "... from a server to another server...". The unclear thing here is exactly how you define "to port". For the database to be restoreable? Nothing has to be done. To not have orphaned users? Well, you don't get orphaned users for Windows
users, only SQL Server users. Is this Windows login already existing in the source database? Does it have permissions assigned for it that you need to keep. If so, why are we talking about crating a *new* users*? Many questions marks here...
Next part: "I need to create an user that doesn't require to accomplish any further user configurations"
Are we talking about creating a user for the purpose of performing the port? Or a user that is expected to use this database after this port? Or does this user exist already?
As for the "doesn't require to accomplish any further user configurations" part, I still don't understand this. Are you asking if all you have to do is to create this Windows user? Then the answer is possibly "yes", but it depends on your answers to my above
questions - i.e. a bigger picture of your scenario and what in the end you are trying to accomplish.
Tibor Karaszi, SQL Server MVP |
web | blog

Created a contained database but unable to connect

Using scripts provided here:
http://blogs.msdn.com/b/sqlsecurity/archive/2010/12/08/contained-database-authentication-in-depth.aspx
Created a contained database in SQL Server Management Studio and a user <domain\user>. and a password.
When trying to look at its properties got this messge,
After fixing the above, I could get the properties and the Select query for the View
sys.dm_db_uncontained_entities
When I try to connect using SQL Server Login;
Server: localhost username & password that of contained database and the default database in login options changed to ContainedDatabase. The authentication is mixed mode.
How do I login?
Jayaram Krishnaswamy

Erland,
Thanks
As to SSMS version:
Microsoft SQL Server Management Studio      11.0.2100.60
Microsoft Data Access Components (MDAC)      6.1.7601.17514
Microsoft MSXML      3.0 4.0 6.0
Microsoft Internet Explorer      9.10.9200.16750
Microsoft .NET Framework      4.0.30319.18408
Operating System      6.1.7601
Toshiba Laptop Windows 7 (x64) Ultimate
From the error message I guessed that default language may not be configured for the contained DB and applied the correction. The funny thing is that stored procedure returned the reply that 1033 was changed to 1033.
The login procedure I used is exactly the way you mentioned which is also mentioned in the quoted article in my original post.
In the connect to server, I specified localhost; SQL Server authentication with the username and password created by the script for the contained database; and in the options changed the default to the name of the contained database. I get a network error
that it cannot find the server.
mysorian

Can DPM 2012 R2 backup SQL Server 2012 AlwaysOn enabled databases

Is it possible to use DPM 2012 R2 for backing up
SQL Server 2012 AlwaysOn enabled databases ?
Because if Alwayson configured for any Database , particular database is not available to select for backup.

Hi,
Yes, starting with DPM 2012 SP1 SQL AlwaysOn enabled databases can be protected as long as they are not part of sharepoint farm. DPM shows the Availability Groups under Cluster Group.
You must explicitly add the system account NTAuthority\System or NT AUTHORITY\DPMRA to the Sysadmin group on SQL Server.
Protecting SQL Server Data
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Mssql collation conflict while update scom 2012 sp1 to r2

hi all
i have scom 2012 sp1 (windows server2008 r2), mssql 2012 sp1 (windows server2008 r2)
while updating scom 2012 sp1 to r2 error is appears:
"DB operations failed with SQL error 468: Cannot resolve the collation conflict between "Cyrillic_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation."
how can i change collation of db "OperationsManager" from "Cyrillic_General_CI_AS" to "SQL_Latin1_General_CP1_CI_AS"?
thanks in advance

For Failed to store data in the Data Warehouse. Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation, you can refer below link
http://thoughtsonopsmgr.blogspot.com/2010/04/failed-to-store-data-in-data-warehouse.html
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

AlwaysOn & Contained Databases Collation Conflict

Similar Messages

Maybe you are looking for