Reportserver Engine changing non-unicode to unicode

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Reporting Services » Reporting Services » Reportserver Engine changing non-unicode to...

Reportserver Engine changing non-unicode to unicode

Rate Topic

Display Mode

Topic Options

Author

Message

curious_sqldba

Posted Friday, January 18, 2013 1:55 PM

Ten Centuries

Group: General Forum Members
Last Login: Yesterday @ 2:47 PM
Points: 1,178, Visits: 2,701

I am experiencing this exact issue as mentioned here [url=http://blogs.msdn.com/b/sql_pfe_blog/archive/2009/06/17/possible-performance-implications-when-using-string-parameters-in-reporting-services.aspx][/url]. I do have a work around. I was wondering is there a setting on the report server or some type of setting on the report server so that we can avoid this conversion?

Post #1409095

curious_sqldba

Posted Monday, January 21, 2013 2:05 PM

Ten Centuries

Group: General Forum Members
Last Login: Yesterday @ 2:47 PM
Points: 1,178, Visits: 2,701

Anyone?

Post #1409709

anthony.green

Posted Tuesday, January 22, 2013 1:48 AM

SSCertifiable

Group: General Forum Members
Last Login: Wednesday, June 05, 2013 2:40 AM
Points: 5,075, Visits: 4,833

There is no report server setting to change the parameters in SSRS from Unicode to Non-Unicode.

Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1409864

wolfkillj

Posted Wednesday, January 23, 2013 11:47 AM

Right there with Babe

Group: General Forum Members
Last Login: Today @ 4:36 AM
Points: 768, Visits: 1,497

sqldba_newbie (1/18/2013)

I've always considered the implementation of multi-value parameters in SSRS to be sub-optimal for this very reason. The most effective workaround, in my view, is to use a stored procedure that accepts the comma-delimited string that SSRS creates from the multi-value parameter and calls a string-splitter function like this one:

http://www.sqlservercentral.com/articles/Tally+Table/72993/

to split the values into a rowset that you can use with an IN condition in the WHERE clause. This way, you can convert the individual parameter values to the same datatype as the column on the other side of the IN, making a SARGable condition that can make use of an appropriate index, if one exists.

Post #1410735

« Prev Topic | Next Topic »

Permissions