March 8, 2012 at 5:05 pm
In our enviroment we all use collation Latin1_General_CI_AS for SQl servers.
So recently when I install a SQl server I found our server is Latin1_General_CI_AS collation, but the reportServer and ReportServerTempdb are automatically created using a different collation: Latin1_General_CI_AS_KS_WS
Then I checked our other Reportserver dbs, I found they are all installed using this collation and not like the server collation.
Why is that?
Will it cause conflict if using tempdb?
March 8, 2012 at 6:07 pm
The simple answer I think is poor design by Microsoft. It would make sense for the ReportServer databases to match the system database collations. The good news is it doesn't impact in the queries in any way. In theory there should be no direct interaction between the ReportServer databases and the user databases and I've never seen an issue between ReportServer and the normal TempDB.
Keep in mind that the ReportServer Service is the application that is interfacing between the ReportServer database and the user databases to extract reports, and that ReportServer is mainly a repository for report deffinitions and cached reports. The actual report you see is being extracted by the application which interacts with the user databases.
It isn't a problem and you can safely ignore it.
Cheers
Leo
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
March 9, 2012 at 9:27 am
Thank you for the information, it is very helpful
March 9, 2012 at 9:43 am
Also I am migrating a SQL 2005 reportserver to a SQL 2008R2 server.
Each server above has database engine and reporting service installed.
After install SQL erver 2008R2, can I do a restore of databases(reportserver db and reportservetempdb from a SQL 2005 to SQL 2008)?
Thanks
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply