As mentioned in the title I am trying to complete the initial config SQL reporting services. When i get to the point I am trying to create the DB it blows up. The default server collation is: SQL_Latin1_General_CP1_CI_AS and I believe this is SQL's default. I have a few other SQL servers running this same default collation and hadn't had a problem setting up reporting services on them - including creating the DB. Anyone have any suggestions? Error below: System.Data.SqlClient.SqlException: The object 'CK_ValidatePromoName' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation. The object 'CK_ValidatePromoNameCheck' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation. The object 'Split' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation. CREATE DATABASE failed. The default collation of database 'ReportServer' cannot be set to 'Latin1_General_CI_AS_KS_WS'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(SqlConnection conn, String script, ICommandWrapperFactory commandWrapper) at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(String connectionString, String script) at ReportServicesConfigUI.SqlClientTools.SqlTools.ApplyScript(String connectionString, String script) SQL version is: Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64) Sep 21 2011 22:45:45 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2) (VM)

Hi ZackinMA, The SQL_Latin1_General_CP1_CI_AS is the default collation for SQL Server, and the Latin1_General_CI_AS_KS_WS is the default collation for Reporting Services. This issue might be caused by the different collation when you create a Report Server database. There are some related thread about this topic, please see: http://qa.social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/ebc6998a-589c-4762-a02b-0b9486ae7138 http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/5225e0ca-5094-4b35-a1ac-eac63bcffb98 For more information about creating a Report Server database, please see: http://technet.microsoft.com/en-us/library/ms157300.aspx Regards, Bin Long TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Bin Long TechNet Community Support

Thanks for getting back to me. Sadly I have already reviewed this info and it didn't help me. I followed the procedure in http://technet.microsoft.com/en-us/library/ms157300.aspx exactly. On that doc under To create a local report server database I get to the last step and BoOM - it blows up as shown: The error is this: System.Data.SqlClient.SqlException: The object 'CK_ValidatePromoName' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation. The object 'CK_ValidatePromoNameCheck' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation. The object 'Split' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation. CREATE DATABASE failed. The default collation of database 'ReportServer' cannot be set to 'Latin1_General_CI_AS_KS_WS'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(SqlConnection conn, String script, ICommandWrapperFactory commandWrapper) at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(String connectionString, String script) at ReportServicesConfigUI.SqlClientTools.SqlTools.ApplyScript(String connectionString, String script) Any other suggestions?

The same error just happened to me tonight while running the Reporting Services Configuration Wizard at the create databases step. It turned out that we put some stored procedures and functions in the Model database, which is used as the template when SQL Server creates a new database, and those objects were preventing the server from changing the collation of the new database ZackinMA - Try dropping the 'CK_ValidatePromoName' object from your Model database, and then run the wizard again. Make sure to script the object and/or take a backup first so you can undo the change if necessary. Good luck! Jason

I ended up just copying a reporting server DB from another server. But I think you're onto something - the model DB on that server is full of stuff we commonly use in development. So even though i found a work around I'm fairly certian you're right. Thanks for the feedback. This thread will no doubt help others in the future who find it on google.