SQL REPORTING SERVICES 2008 R2

I HAVE THIS QUERY:
SELECT     DIMENSIONS.DESCRIPTION, HOS_SALEHST.CUSTOMERCLASS, MONTH (HOS_SALEHST.INVOICEDATE) as MONTH,
YEAR (HOS_SALEHST.INVOICEDATE) as YEAR, HOS_SALEHST.ITEMCLASS, SUM(HOS_SALEHST.QUANTITY) AS QUANTITY, SUM(HOS_SALEHST.NETSALESAMOUNT)
                      AS NETSALESAMOUNT
FROM         HOS_SALEHST INNER JOIN
                      DIMENSIONS ON HOS_SALEHST.DATAAREAID = DIMENSIONS.DATAAREAID AND HOS_SALEHST.ITEMCLASS = DIMENSIONS.NUM
WHERE     (HOS_SALEHST.INVOICEDATE >= '1/1/2013') AND (HOS_SALEHST.INVOICEDATE < '4/1/2014') AND (HOS_SALEHST.ITEMCLASS <= 1985) AND
                      (HOS_SALEHST.ITEMCLASS <> '') AND (DIMENSIONS.DIMENSIONCODE = 1) AND ((HOS_SALEHST.COMPANYNUM >= 02 AND
HOS_SALEHST.COMPANYNUM <= 07 AND
HOS_SALEHST.CUSTOMERCLASS = 'DS') OR
(HOS_SALEHST.COMPANYNUM = 01 AND
HOS_SALEHST.CUSTOMERCLASS <> 'DC'))
GROUP BY HOS_SALEHST.CUSTOMERCLASS,HOS_SALEHST.ITEMCLASS, DIMENSIONS.DESCRIPTION, MONTH(HOS_SALEHST.INVOICEDATE), YEAR(HOS_SALEHST.INVOICEDATE)
ORDER BY HOS_SALEHST.ITEMCLASS
I want to have it where the SALEHST.CUSTOMERCLASS will pull in the lines t that are 'ES' or 'EC' as EXP but all others pull in as they are.
I tried using the CASE ELSE below but can't get it to work. Maybe it's not the right approach???
SELECT     DIMENSIONS.DESCRIPTION, HOS_SALEHST.CUSTOMERCLASS, MONTH (HOS_SALEHST.INVOICEDATE) as MONTH,
YEAR (HOS_SALEHST.INVOICEDATE) as YEAR, HOS_SALEHST.ITEMCLASS, SUM(HOS_SALEHST.QUANTITY) AS QUANTITY, SUM(HOS_SALEHST.NETSALESAMOUNT)
AS NETSALESAMOUNT
FROM         HOS_SALEHST INNER JOIN
DIMENSIONS ON HOS_SALEHST.DATAAREAID = DIMENSIONS.DATAAREAID AND HOS_SALEHST.ITEMCLASS = DIMENSIONS.NUM
WHERE     (HOS_SALEHST.INVOICEDATE >= '1/1/2013') AND (HOS_SALEHST.INVOICEDATE < '4/1/2014') AND (HOS_SALEHST.ITEMCLASS <= 1985) AND
(HOS_SALEHST.ITEMCLASS <> '') AND (DIMENSIONS.DIMENSIONCODE = 1) AND ((HOS_SALEHST.COMPANYNUM >= 02 AND
HOS_SALEHST.COMPANYNUM <= 07 AND
HOS_SALEHST.CUSTOMERCLASS = 'DS') OR
(HOS_SALEHST.COMPANYNUM = 01 AND
HOS_SALEHST.CUSTOMERCLASS <> 'DC',
CASE SALEHST.CUSTOMERCLASS
WHEN 'EC' OR 'ES' THEN 'EXP'
ELSE 'SALEHST.CUSTOMERCLASS'))
GROUP BY HOS_SALEHST.CUSTOMERCLASS,HOS_SALEHST.ITEMCLASS, DIMENSIONS.DESCRIPTION, MONTH(HOS_SALEHST.INVOICEDATE), YEAR(HOS_SALEHST.INVOICEDATE)
ORDER BY HOS_SALEHST.ITEMCLASS
Really appreciate your help.

Dominic,
I really appreciate your help. I think you understand what I need. My customer class could be a possibility of six different outcomes but I want of the six outcomes
for two of them to be joined into one - the EXP.
I am getting a syntax error: Incorrect syntax near the keyword 'OR', Incorrect syntax near the keyword 'ELSE', Incorrect syntax near the keyword 'AND', (Microsoft SQL Server,
Error: 156)
This is how I have the code now. Do you see what I have wrong please?
DECLARE @IsEXP BIT
SET @IsExp =
        CASE SALEHST.CUSTOMERCLASS
        WHEN 'EC' OR 'ES' THEN 1 --Yes, 'EXP' should be used
        ELSE 0 --No, use the normal value
IF (@IsExp = 0)
BEGIN
SELECT     DIMENSIONS.DESCRIPTION, HOS_SALEHST.CUSTOMERCLASS, MONTH (HOS_SALEHST.INVOICEDATE) as MONTH,
YEAR (HOS_SALEHST.INVOICEDATE) as YEAR, HOS_SALEHST.ITEMCLASS, SUM(HOS_SALEHST.QUANTITY) AS QUANTITY, SUM(HOS_SALEHST.NETSALESAMOUNT)
                       AS NETSALESAMOUNT
FROM         HOS_SALEHST INNER JOIN
                       DIMENSIONS ON HOS_SALEHST.DATAAREAID = DIMENSIONS.DATAAREAID
AND HOS_SALEHST.ITEMCLASS = DIMENSIONS.NUM
WHERE     (HOS_SALEHST.INVOICEDATE >= '1/1/2013') AND (HOS_SALEHST.INVOICEDATE < '4/1/2014') AND (HOS_SALEHST.ITEMCLASS <= 1985) AND
                       (HOS_SALEHST.ITEMCLASS <> '')
AND (DIMENSIONS.DIMENSIONCODE = 1) AND ((HOS_SALEHST.COMPANYNUM >= 02 AND
HOS_SALEHST.COMPANYNUM <= 07 AND
HOS_SALEHST.CUSTOMERCLASS = 'DS') OR
(HOS_SALEHST.COMPANYNUM = 01 AND
HOS_SALEHST.CUSTOMERCLASS <> 'DC'))
GROUP BY HOS_SALEHST.CUSTOMERCLASS,HOS_SALEHST.ITEMCLASS, DIMENSIONS.DESCRIPTION, MONTH(HOS_SALEHST.INVOICEDATE), YEAR(HOS_SALEHST.INVOICEDATE)
ORDER BY HOS_SALEHST.ITEMCLASS
ELSE IF (@IsExp = 1)
SELECT     DIMENSIONS.DESCRIPTION, HOS_SALEHST.CUSTOMERCLASS, MONTH (HOS_SALEHST.INVOICEDATE) as MONTH,
YEAR (HOS_SALEHST.INVOICEDATE) as YEAR, HOS_SALEHST.ITEMCLASS, SUM(HOS_SALEHST.QUANTITY) AS QUANTITY, SUM(HOS_SALEHST.NETSALESAMOUNT)
                       AS NETSALESAMOUNT
FROM         HOS_SALEHST INNER JOIN
                       DIMENSIONS ON HOS_SALEHST.DATAAREAID = DIMENSIONS.DATAAREAID
AND HOS_SALEHST.ITEMCLASS = DIMENSIONS.NUM
WHERE     (HOS_SALEHST.INVOICEDATE >= '1/1/2013') AND (HOS_SALEHST.INVOICEDATE < '4/1/2014') AND (HOS_SALEHST.ITEMCLASS <= 1985) AND
                       (HOS_SALEHST.ITEMCLASS <> '')
AND (DIMENSIONS.DIMENSIONCODE = 1) AND ((HOS_SALEHST.COMPANYNUM >= 02 AND
HOS_SALEHST.COMPANYNUM <= 07 AND
HOS_SALEHST.CUSTOMERCLASS = 'DS') OR
(HOS_SALEHST.COMPANYNUM = 01 AND
HOS_SALEHST.CUSTOMERCLASS <> 'DC'))
GROUP BY HOS_SALEHST.CUSTOMERCLASS,HOS_SALEHST.ITEMCLASS, DIMENSIONS.DESCRIPTION, MONTH(HOS_SALEHST.INVOICEDATE), YEAR(HOS_SALEHST.INVOICEDATE)
ORDER BY HOS_SALEHST.ITEMCLASS AND
                HOS_SALESHST.CUSTOMERCLASS<>'EXP'
END
DECLARE @IsEXP BIT
SET @IsExp =
        CASE SALEHST.CUSTOMERCLASS
        WHEN 'EC' OR 'ES' THEN 1 --Yes, 'EXP' should be used
        ELSE 0 --No, use the normal value
IF (@IsExp = 0)
BEGIN
SELECT     DIMENSIONS.DESCRIPTION, HOS_SALEHST.CUSTOMERCLASS, MONTH (HOS_SALEHST.INVOICEDATE) as MONTH,
YEAR (HOS_SALEHST.INVOICEDATE) as YEAR, HOS_SALEHST.ITEMCLASS, SUM(HOS_SALEHST.QUANTITY) AS QUANTITY, SUM(HOS_SALEHST.NETSALESAMOUNT)
                       AS NETSALESAMOUNT
FROM         HOS_SALEHST INNER JOIN
                       DIMENSIONS ON HOS_SALEHST.DATAAREAID = DIMENSIONS.DATAAREAID
AND HOS_SALEHST.ITEMCLASS = DIMENSIONS.NUM
WHERE     (HOS_SALEHST.INVOICEDATE >= '1/1/2013') AND (HOS_SALEHST.INVOICEDATE < '4/1/2014') AND (HOS_SALEHST.ITEMCLASS <= 1985) AND
                       (HOS_SALEHST.ITEMCLASS <> '')
AND (DIMENSIONS.DIMENSIONCODE = 1) AND ((HOS_SALEHST.COMPANYNUM >= 02 AND
HOS_SALEHST.COMPANYNUM <= 07 AND
HOS_SALEHST.CUSTOMERCLASS = 'DS') OR
(HOS_SALEHST.COMPANYNUM = 01 AND
HOS_SALEHST.CUSTOMERCLASS <> 'DC'))
GROUP BY HOS_SALEHST.CUSTOMERCLASS,HOS_SALEHST.ITEMCLASS, DIMENSIONS.DESCRIPTION, MONTH(HOS_SALEHST.INVOICEDATE), YEAR(HOS_SALEHST.INVOICEDATE)
ORDER BY HOS_SALEHST.ITEMCLASS
ELSE IF (@IsExp = 1)
SELECT     DIMENSIONS.DESCRIPTION, HOS_SALEHST.CUSTOMERCLASS, MONTH (HOS_SALEHST.INVOICEDATE) as MONTH,
YEAR (HOS_SALEHST.INVOICEDATE) as YEAR, HOS_SALEHST.ITEMCLASS, SUM(HOS_SALEHST.QUANTITY) AS QUANTITY, SUM(HOS_SALEHST.NETSALESAMOUNT)
                       AS NETSALESAMOUNT
FROM         HOS_SALEHST INNER JOIN
                       DIMENSIONS ON HOS_SALEHST.DATAAREAID = DIMENSIONS.DATAAREAID
AND HOS_SALEHST.ITEMCLASS = DIMENSIONS.NUM
WHERE     (HOS_SALEHST.INVOICEDATE >= '1/1/2013') AND (HOS_SALEHST.INVOICEDATE < '4/1/2014') AND (HOS_SALEHST.ITEMCLASS <= 1985) AND
                       (HOS_SALEHST.ITEMCLASS <> '')
AND (DIMENSIONS.DIMENSIONCODE = 1) AND ((HOS_SALEHST.COMPANYNUM >= 02 AND
HOS_SALEHST.COMPANYNUM <= 07 AND
HOS_SALEHST.CUSTOMERCLASS = 'DS') OR
(HOS_SALEHST.COMPANYNUM = 01 AND
HOS_SALEHST.CUSTOMERCLASS <> 'DC'))
GROUP BY HOS_SALEHST.CUSTOMERCLASS,HOS_SALEHST.ITEMCLASS, DIMENSIONS.DESCRIPTION, MONTH(HOS_SALEHST.INVOICEDATE), YEAR(HOS_SALEHST.INVOICEDATE)
ORDER BY HOS_SALEHST.ITEMCLASS AND
                HOS_SALESHST.CUSTOMERCLASS<>'EXP'
END
Thanks a ton!
Tracy

Similar Messages

Expand and Collapse(+/-) option in a Matrix SQL Reporting Services 2008

Hello All,
I am having Expand and Collapse(+/-) option in a Matrix SQL Reporting Services 2008. It's not working when it is havnig a Row Group and Column Group.
Does reporting services has this flexibulity?? It's working fine if it's only have a Row Group an it's not working if it is having Row and a Column Group. Can any one suggest how to work aroung with this.
any help much appriciated.
Thanks & Regards,
Jeevan Dasari.
Dasari

Drill-down feature is a basic requirement, it is concluded in Reporting service from SSRS2000 to SSRS2008 R2, To
your scenario I think the root cause is relevant to your incorrect steps. Please follow the steps below and then give the feedback:
1.     Right-click the child groups in the
Row Groups panel which is at the left-bottom of the BIDS, and then select
Group Properties…
2.
Switch to Visibility tab, and then select
Hide Radio-button, click the checkbox of Display can be toggled by this report item.
3.
Then select the parent group datafield in the drop-down list.
4.
Click OK.
Thanks,
Challen Fu
Challen Fu [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

SQL Reporting Services 2014, Enabling Kerberos causes report manager to be extremely slow

We are migrating our environment from SQL Reporting Services 2008 to 2014 on a new server. We are currently using kerberos on the 2008 instance, but when I enable kerberos on the 2014 Reporting Services instance the Report Manager becomes extremely slow.
Has anyone seen this before? Any ideas of what I can check to see what is causing this problem.

Just to clarify it is not slow when I run a report, it is slow in general. From first load to accessing a folder, settings, etc. This is all before even executing a report.
The error I see while using Wireshark is KRB Error: KRB5KDC_ERR_BADOPTION NT Status: STATUS_NO_MATCH. When I drill down the into the
error I can see the kerberos string is testprjmnmtreports14.company.com, which is the URL we are using to access the site. I made sure to add that name as an SPN for the service account that is running SQL Reporting Services, however I still receive the error.
Then I tried configuring the site to run without a hostheader, so I accessed the site with the server name ECTSTSQLRS5 and the site works perfectly fine, no errors are reported either. So it seems I have isolated the issue down to Kerberos but I am not sure
how to resolve it. Here is some more information about my environment:
DNS/URL used: testprjmnmtreports14.company.com
Server Name (FQDN): ECTSTSQLRS5.company.int
AD Domain Name: company.int
Server Version: Windows Server 2012 R2
AD Functional Level: 2008 R2
I also have the following SPNs set for my SQL service account:
http/testprjmngmtreports14.company.com
http/testprjmngmtreports14
http/ECTSTSQLRS5.COMPANY.INT
http/ECTSTSQLRS5
As you can see I am trying to use a .com address but my AD domain is .int which I think is the issue, but I do not have the same problem on my other server that is running Windows Server 2008 R2.

Report Builder 1.0 for SQL Server Reporting Services 2008 R2

We are trying to implement Ad-Hoc Reporting using SSRS 2008 R2.
First of all, it is very unhelpful that all SSRS books are for either 2008 or 2012, even though SSRS has major changes in 2008 R2 compared to 2008.
Our instructional materials indicate that we should build Report Models to abstract out our databases into terms familiar to our business users.
The problem we are having is the difference in functionality between Report Builder 1.0 and Report Builder 3.0. Report Builder 3.0 is touted as having the modern, ribbon based interface that is supposed to make end-users feel more comfortable. However,
all the documentation says that end users are supposed to use Report Builder 1.0 for Ad-Hoc Reporting. And, it seems, that the reports generated by Report Builder 1.0 are not round-trip compatible with all the other reporting tools for SSRS 2008 R2.
The documentation we have illustrates that Report Builder 1.0 is nice for Ad-Hoc reporting, because is based on connecting directly to Report Models, and the end users can directly drag-and-drop entities and fields into their reports.
When we try working with Report Builder 3.0, it seems we must first connect to the Report Model as a Data Source and then build a Dataset query on the Report Model. Only then are some entity attributes available to be dropped into the report.
If the user decides another source column is needed, they have to go back, edit the query, save the query, and then drag the column from the Dataset to the report. This does not seem end user friendly at all!
We are also concerned that if we train our users on the seemingly soon-to-be-obsolete Report Builder 1.0, and get them used to having direct Report Model access, that at some point we will have to move them to the Dataset-interrupted approach of Report Builder
2+. Highlighting this perception of impending obsolescence of Report Builder 1.0 is that in our shop that is starting with SSRS 2008 R2, we cannot figure out how to get a copy of Report Builder 1.0 in the first place.
We just don't see our end users being savvy enough to handle the steps involved with creating Datasets on top of Report Model Data Sources. So we would have to build the Datasets for them. But in that case, what point is there in creating any
Report Models in the first place if DBAs are the ones to make Datasets?
As such, it is hard to envision a forward-looking SSRS implementation that has the end user ease-of-use Ad-Hoc reporting that the SSRS 2008 documentation presents.
What is it that Microsoft actually wants/expects SSRS implementers to do?
Dan Jameson
Manager SQL Server DBA
CureSearch for Children's Cancer
http://www.CureSearch.org

Hi Dan,
Report Builder 1.0
Simple template-based reports
Requires report model
Supports only SQL Server, Oracle, and Analysis Services as data sources
Supports RDL 2005
Bundled in SSRS
Report Builder 2.0 or later
Full-featured reports as the BIDS Report Designer
Doesn't require (but supports) report models
Supports any data source
Supports RDL 2008
Available as a separate web download
In your scenario, you want to use Report Builder 1.0 in SQL Server Reporting Services 2008 R2, I am afraid this cannot achieve. Report Builder 1.0 is available in the box in either SQL 2005 or SQL 2008. It is not available as a separate client apps and is
only available as a click once application.
Report Builder 1.0
Report Builder 3.0
Thank you for your understanding.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Upgrade Sharepoint 2010 SQL Reporting Services from 2008 R2 to 2014

I'm about to do the upgrade of SharePoint 2010 Reporting Services from 2008 R2 to 2014. The instructions say it can be done "in-place" with no downtime. I've seen this article:
http://whitepages.unlimitedviz.com/2012/03/upgrading-sql-server-reporting-services-to-2012-in-sharepoint-integrated-mode/
It covers 2012 so I assume the same holds true for 2014.
I'd like to get the low down from anyone who has actually performed the upgrade of SSRS from 2008 R2 to 2014. Anyone done this upgrade? Any issues?
David Jenkins

So far I would have to say that the upgrade can be done "in-place" but there is a "DOWNTIME".
This article has helped a lot:
http://blogs.catapultsystems.com/tlingenfelder/archive/2012/07/10/upgrading-sql-server-reporting-services-2008-r2-to-sql-server-reporting-services-2012-in-sharepoint.aspx
In the article it tells you about a bug in the SQL Upgrade process where
the Domain account you use will not work. When you type in the password it fails. On top of that it will lock the Domain account because of a bad password! There is probably something wrong with the authentication process and it garbles the password.
Anyway, you end up having to change the account to the "Network Service" account before you can do the upgrade. This means the services get restarted which means???
DOWN TIME! He goes over other errors. I haven't reviewed these issues yet.
The other thing I learned is that everything needs to be SQL Server 2008 R2 SP2 in order to upgrade. You don't find this out until almost the last step in the installation process.
Now I have to wait until next week to actually do the upgrade because I have to schedule an SP2 install. :(
David Jenkins

How to Convert MM/DD/YYYY to YYYY/MM/DD in SQL Reporting Services

i am having difficulty of converting a parameter field, called @startdate, on sql reporting services report to YYYY/MM/DD format. the parameter @Startdate was set to Data/Time. @Startdate is 6/1/2014 12:00:00 and I want to convert it
to 2014/06/01. I want to compare @Startdate with a column in database called Begindate which is in format of YYYY/MM/DD hh:mm:ss. I tried the followings
select * from Atable where cast(Atable.Begindate as date) >= cast(@Startdate as date)
select * from Atable where cast(Atable.Begindate as date >= cast(convert(datetime, @Startdate) as date)
SQL Reporting Services only gives me Text, Boolean, Date/Time, Integer and Float.
Regards,

Hi Elmucho,
Sorry for the delay. I tested with the sample data you provided, however everything works well in-house. Could you please creste a new report and check the result. Here are the steps I performed:
1. Create a table and insert the following data:
Name (varchar(50))    Begindate (datetime, not null)
Lastdate (datetime, not null)
bob
2008-01-01 08:08:08.000      2010-10-10
10:10:10.000
alice
2010-10-10 10:10:10.00       2011-11-11
  11:11:11.000
smith
2011-11-11 11:11:11.00       2012-12-12
12:12:12.000
2. Open SQL Server Data Tools, create the data source and add the dataset with the below query:
SELECT     Name, Begindate, Lastdate
FROM         [tablename ]
WHERE     (CAST(Begindate AS date) >= CAST(@Startdate AS date)) AND (CAST(Lastdate AS date) <= CAST(@Enddate AS date))
3. Then, click execute button, it prompts for inputting the parameter value.
@Startdate
6/1/2008
@Enddate
5/1/2014
Enter the date and press OK.
4. Here is the result in the query designer:
Insert a table and fields. Save the report and preview:
Thanks.
Tracy Cai
TechNet Community Support

How to set a default date as a parameter in Microsoft Reporting Services 2008 to January 1st

How can I set a default parameter for date for 01/01/yyyy.

Hi Giss68,
If I understand correctly, you want to set the first day of current year as a default value of a parameter in Microsoft Reporting Services 2008 report.
If in this scenario, we can use the expression below as the default value in the parameter:
=DateAdd("d",-DatePart(DateInterval.DayOfYear,Today,0,0)+1,Today)
The following document about DateAdd function is for your reference:
http://technet.microsoft.com/en-us/library/aa337194(v=sql.100).aspx
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

Upgrade 2010 to 2013 with SQL Reporting Services

I'm getting ready to upgrade to 2013.
When I run the Test-SPContentDatabase I get:
Category : MissingWebPart
Error : True
UpgradeBlocking : False
Message : WebPart class [ab6d9dad-e23c-ce4f-ff98-f6575a1ccf4c] (class [
Microsoft.ReportingServices.SharePoint.UI.WebParts.ReportView
erWebPart] from assembly
[Microsoft.ReportingServices.SharePoint.UI.WebParts,
Version=10.0.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91]) is referenced [24] times
in the database [is-sharepoint], but is not installed on the
current farm. Please install any feature/solution which
contains this web part.
Remedy : One or more web parts are referenced in the database
[is-sharepoint], but are not installed on the current farm.
Please install any feature or solution which contains these
web parts.
Locations :
Category : MissingAssembly
Error : True
UpgradeBlocking : False
Message : Assembly
[Microsoft.ReportingServices.SharePoint.UI.ServerPages,
Version=10.50.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91] is referenced in the
database [is-sharepoint], but is not installed on the
current farm. Please install any feature/solution which
contains this assembly.
Remedy : One or more assemblies are referenced in the database
[is-sharepoint], but are not installed on the current farm.
Please install any feature or solution which contains these
assemblies.
Locations :
Category : Configuration
Error : False
UpgradeBlocking : False
Message : The [is.photomask.com] web application is configured with
claims authentication mode however the content database you
are trying to attach is intended to be used against a
windows classic authentication mode.
Remedy : There is an inconsistency between the authentication mode of
target web application and the source web application.
Ensure that the authentication mode setting in upgraded web
application is the same as what you had in previous
SharePoint 2010 web application. Refer to the link
"http://go.microsoft.com/fwlink/?LinkId=236865" for more
information.
Locations :
The first two have to do with reporting services. I'm trying to workout how to go about getting these errors to go away. I don't want to remove SQL reporting or migrate a broken site and fix it later. FYI it does migrate but reporting services
is of course broken.
So what I was wanting to do was to upgrade SQL Reporting Services for SharePoint 2010 from 2008 SQL to 2014 SQL first. This would be in the hopes that it would make the migration to SharePoint 2013 work as the assemblies would change to the proper
version.
Can anyone elaborate on my upgrade path?
I'm still looking up the "Claims Based" authentication thing. I've found an article on how to migrate it so not a big deal. I do wonder however if this is tied to the issue I saw with default.aspx and home.aspx being denied to all users
after I did migrate a content db.
David Jenkins

Hi David,
The following sections describe the basic steps needed to upgrade or migrate from 2008 versions of Reporting Services SharePoint mode to 2014 version.
SQL Server 2008 R2 to SQL Server 2014
Starting environment: SQL Server 2008 R2, SharePoint 2010.
Ending environment: SQL Server 2014, SharePoint 2010.
In-place upgrade is supported and there is no down time for your SharePoint environment.
Install the SQL Server 2014 version of the Reporting Services add-in for SharePoint on each web front-end in the farm. You can install the add-in by using the SQL Server 2014 installation wizard or by downloading the add-in.
Run SQL Server 2014 installation to upgrade SharePoint mode for each “report server”. The SQL Server installation wizard will install the Reporting Services Service and create a new Service application.
If you also want the ending environment to run SharePoint 2013, you need to complete a database-attach upgrade of the SharePoint 2010 to SharePoint 2013.
For more scenarios information, please refer to:
http://msdn.microsoft.com/en-us/library/ms143747.aspx#bkmk_sharePoint_scenarios
Per the supported combinations of SharePoint and Reported Services Components, I’d recommend you firstly upgrade Reporting Services to 2014, then upgrade SharePoint to 2013.
For more information:
http://msdn.microsoft.com/en-us/library/gg492257.aspx
The link below is the reference for migrating a Reporting Services:
http://msdn.microsoft.com/en-us/library/hh759331.aspx
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Add SQL reporting services to get Azure sql db data

Dear all,
I have read recently that SQL server reporting services as been remmoved from Azure services. I have a SQL server database on azure which collect different type of data which are collected from a web admin portal by my users.
I have a strong need to bring to that admin web portal a flexible reporting solution for my users to monitor collected data.
Of course I can bring dash board to web application but often it is painful to change web app when a user want different type of report.
What could be the way now to use online reporting service in orde to bring online report for my user of my sql azure database ?
regards
serge

Hi serge,
Based on my understanding, you want to use SQL Azure database to design the report, right?
As you mentioned,
Azure SQL Reporting is officially discontinued, so that we can’t design reports with Azure SQL Reporting. However, only the Azure cloud implementation of SQL Reporting is discontinued. All other forms of Reporting Services technology are unaffected. In
Reporting services, it’s supported connect to SQL Azure database. So in your scenario, you can connect to the SQL Azure database to design the report. For more information, please refer to this article:
How to connect to SQL Azure using SQL Server Reporting Services 2008 R2.
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

SQL Reporting Services with Visual Studio 2012

Hi
I would like to know if there will be any release to improve on the placeholder feature in SQL reporting services. Currently, I have users who uses HTML editor to input data and tables. However, the table in html format cannot be read.
I do understand that currently the placeholder feature can only have limited html tag recognised. However, is there any plan to improve it so that <table> tag can also be recognise?
Or if there is any workaround to show the table format in the reports?
Sorry but this is urgent as it is used for business application.
Many thanks

Hi DotNeTEngineeR,
According to description, you want to display the content of table tag (<tag>) in a report. Right?
In Reporting Services, it only has the supported HTML Tags below:
Hyperlinks: <A HREF>
Fonts: <FONT>
Header, style and block elements: <H{n}>, <DIV>, <SPAN>,<P>, <DIV>, <LI>, <HN>
Text format: <B>, <I>, <U>, <S>
List handling: <OL>, <UL>, <LI>
For your requirement, we suggest you use <div> to replace <table> tags in your embedded HTML. Please see the article below:
Embedded HTML using <div> to replace <table> tags in ssrs 2008
Reference:
Importing HTML into a Report (Report Builder and SSRS)
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Reporting Services 2008 R2 - SharePoint Integration Mode

Hi everyone,
I installed Reporting Services 2008 R2 in my SharePoint(2013) server and configurated the SSRS to run in SharePoint Integrate mode. But, when I run the command Install-SPRSService in SharePoint 2013 Management Shell, I get this error:
Does anyone know how resolve it ? I search but I didn't get a solution :(
Thanks in advance!
Best Regards!

SSRS 2008 R2 isn't supported with SharePoint 2013. You'll need a minimum of SSRS 2012 SP1. In addition, SSRS 2008 R2 doesn't include the cmdlet you're looking for because it isn't a Service Application, rather it sat external to SharePoint.
The support matrix is at http://msdn.microsoft.com/en-us/library/gg492257.aspx.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Workflows 2013 and SQL Report Services: Configure on Independent Servers or Existing App Servers?

Currently, my SharePoint 2013 Farm has Workflows 2013 and SQL Report Services installed on app servers, along with other applications. Workflows 2013 isn't working correctly (installed prior to my coming on board with the organization), I'm assuming it
is a configuration issue, but rather than re-configure, I've read that is recommended to be a standalone server. It was also recommended by a MSFT rep that our report services have its own independent server. Currently, Report Services is also installed on
an app server that runs other applications on the farm.
Has anyone had any experience with installing Workflows 2013 and/or SQL Report Services on independent vs. existing application servers?
Additionally, my existing application servers have 24 GB of RAM (I believe the recommendation for SharePoint production environments is 12 GB), should I plan for the potentially new servers (Workflows and Report Services) to also have 24 GB of RAM? Not really
sure if it will be needed if they have dedicated tasks.
Thanks for any input you can provide!

It entirely depends on load. WFM will work just fine installed on servers in the SharePoint farm. SSRS preferably should go on the end-user facing servers for better performance.
The questions you're asking are all "it depends" :)
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Installed SQL Reporting Services 2012 on SharePoint 2013 Server. SQL Reporting Service not available In the list of runnning services or new service applications

Hi I'm trying to setup SQL reporting services in a SharePoint 2013 farm consisting of:
4 WFE's
4 App Servers (NLB Central Admin x 4 servers)
4 App Severs for SSRS (Light limited SharePoint services running)
I've installed SSRS 2012 SP1 by following the guide (http://msdn.microsoft.com/en-us/library/gg492276.aspx) on one of the SSRS SharePoint 2013 servers and ensuring Reporting Services - SharePoint and Reporting Services Add-in for SharePoint Products is selected.
All completed without errors and I have even upgraded to SP2 for troubleshooting but no joy.
I've then gone into SharePoint Central Admin and I cannot see SQL Reporting Service available In the list of runnning services on the server I have just installed SSRS on and going to manage service applications I cannot see in the new dropdown menu SQL
Reporting Services.
I have ran the following commands in the SHarePoint management shell:
Install-SPRSService and Install-SPRSSeviceProxy
and
get-spserviceinstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance
The reply was that the service was already online on the server.
So in powershell all seems ok but it does not appear in central administration.
I have also moved Central Administration to the SSRS SharePoint server too.
Any other suggestions? Here is the same problem but in SP2010 (http://social.technet.microsoft.com/Forums/office/en-US/6a21cc05-1f9b-49ad-a9bb-44aa5b3ce312/action?threadDisplayName=after-installing-sql-reporting-services-service-for-sharepoint-2012-service-is-not-in-the-list-of)
In my lab environment of a 4 server SP2013 farm it worked immediately when i installed it on the app server (CA host) so I dont think it is my install strategy.
I guess my next attempt is to install SSRS on an app server with central administration hosted.
Thanks

I had the same issue on 2 different environments.
I had 2 application servers. One had Central Administration. I installed SSRS on the other one and it never appeared in the Service Applications in SharePoint.
When I also provisioned Central Administration on the other application server and went to the service applications using Central Admin on that server, the SSRS service application was there.
Since then I always install SSRS on the server which hosts Central Admin. No issues then.

FQDN or NetBIOS for SQL Reporting Services Point installation in a cluster

Hi Folks
We have a SQL cluster for config mgr database & SQL reporting services installed on nodes because it is not cluster aware. During SCCM 2012 installation, we mentioned the details of SQL cluster only & it got installed successfully. When we checked
in console, it is showing 3 site servers related to SQL. SQL cluster is having site system role only & site database role moved under 2 nodes. Only NetBIOS names of the SQL nodes are being displayed in console.
Now when I installed reporting service point role by selecting one of the node, wizard picks the FQDN of this node automatically & role installed successfully.
Now in the console, I have another site server listed publishing the FQDN of the same node which I selected during installation which means one SQL node (site database role present at this) is displaying with NetBIOS name & the same SQL node
(reporting services point role at this) is displaying with FQDN.
My concerns is that -
Is there any issue if same SQL node displaying 2 times in SCCM console i.e. with NetBIOS name & with FQDN name?
Why reporting services point role not placed under the node which is already there with NetBIOS name?
I hope I explained my issue properly however If you guys need any more information regarding this, then let me know.
Cheers | Navdeep Sidhu

This is the default behavior when installing site DB on cluster - all nodes will be visible as NetBIOS.
I face a problem in two separate environments with SQL cluster when configuring Auto client push for servers, you will get the following error message in CCM.log in site server:
SQL Server Native Client 11.0][SQL Server]Invalid length parameter passed to the LEFT or SUBSTRING function. : sp_CP_CheckNewAssignedMachine
AND
Failed to execute SQL cmd exec [sp_CP_CheckNewAssignedMachine]
I believe this is a bug in the product.
There is a workaround FIX editing the SP in SQL DB but it is UNSUPPORTED.

Service Manager data warehouse SQL Reporting Services server is currently unavailable

I keep getting this error when I launch my SCSM Console. Take a look at the event log > operation manager and saw this error message below.
Tried to google around but unable to find any solution to it. Anybody can enlighten me on this issue that I am encountering? Thanks
Cannot connect to SQL Reporting Services Server. Message= An unexpected error occured while connecting to SQL Reporting Services server: System.Net.WebException: The request failed with HTTP status 404: Not Found.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.EnterpriseManagement.Reporting.ReportingService.ReportingService2005.FindItems(String Folder, BooleanOperatorEnum BooleanOperator, SearchCondition[] Conditions)
at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItems(String searchPath, IList`1 criteria, Boolean And)
at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItems(String itemPath)
at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItem(String itemPath, ItemTypeEnum[] desiredTypes)
at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.GetFolder(String path)
at Microsoft.EnterpriseManagement.Reporting.EnterpriseReportingGroup.Initialize()
at Microsoft.EnterpriseManagement.Reporting.ServiceManagerReportingGroup..ctor(DataWarehouseManagementGroup managementGroup, String reportingServerURL, String reportsFolderPath, NetworkCredential credentials)
at Microsoft.EnterpriseManagement.Reporting.ServiceManagerReportingGroup..ctor(DataWarehouseManagementGroup managementGroup, String reportingServerURL, String reportsFolderPath)
at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ManagementGroupServerSession.TryConnectToReportingManagementGroup() Remediation = Please contact your Administrator.
Jeron

Hi,
This may occur when there is a mismatch between the Report Server URL entered on the SSRS Server Location window for the Report Deployment Wizard and the SSRS Web Service Virtual Directory for the Reporting
Services Configuration Manager.
Use the following steps to resolve the issue:
Launch the Reporting Services Configuration Manager on the server hosting SSRS
Select Web Service URL
Copy the value entered in the Virtual Directory textbox
Paste it after the last forward slash in the Report Server URL textbox in the Report Deployment Wizard
Continue on with the deployment
In addition, we may need to check you default web server IP is 'all unassigned', and ping the machine and see what default ip it has assigned.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

SQL REPORTING SERVICES 2008 R2

Similar Messages

Maybe you are looking for