May 5, 2014 at 3:16 am
Hi
I have setup db containment with a different Collation that the TempDB and it works perfectly when using temptables. However, when I try to run a script with links a table on my contained db with systable, example sys.allobjects I still get the collation error. I or now added "COLLATE database_default" for the fields which is causing the error on the join. I know we do not link to the the systables a lot so it's easier using db containment where we have a lot of collation issues when working with temptables.
The option is not available to change collation to be the same as the system databases.
Another question I have is, our database is currently using Latin1_General_BIN. Our system db's are on Latin1_General_CI_AS. This DB ontainment is OK and working here. What happens if we add Reporting services db which uses Latin1_General _CI_AS_KS_WS, will it work using our DB collation,with TempDB and Reporting services collation or are we going to run into trouble. I did actually test this and we do get the following collation error when combining Temp tables with our database and Reporting services
Msg 468, Level 16, State 9, Line 4
Cannot resolve the collation conflict between "Latin1_General_CI_AS_KS_WS" and "Latin1_General_BIN" in the equal to operation.
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply