June 23, 2014 at 2:13 am
We have a live and failover Report Server and I'm currently in the process of making sure that all the reports and procs match across the two. The problem I've come across is that they do actually match exactly and I'm not sure that they should. I've been using Beyond Compare to compare them and I've discovered that in most cases, where I should have a difference there hasn't been one. Each piece of XML I've compared has had a short section and the bottom like so:
<rd:ReportServerUrl>http://MyServer</rd:ReportServerUrl>%5B/quote%5D
That has been the case for all the reports that I've checked on both servers. I was expecting that the XML on one server would have the URL for that server and the XML on the other would have the corresponding URL ie
<rd:ReportServerUrl>http://MyOtherServer</rd:ReportServerUrl>%5B/quote%5D
Some of the reports have what I think is the correct URL but the majority of them don't. When I investigated the reports manually everything appeared correct and both versions ran on the appropriate servers. Can anybody shed any light on this please? If you need more information just ask.
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
June 23, 2014 at 3:23 pm
This is bad form I know but can anybody help? Has anybody seen anything like this before? We're looking at a bit of investment and the answer to this question will affect whether or not the dynamite is used on the company wallet fastener.
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
June 23, 2014 at 5:28 pm
That property comes from ReportDesigner, and is used to identify the original source of the report.
I don't believe it is relevant for the everyday running of a report as ReportServer will not even read that property.
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);
June 24, 2014 at 1:00 am
Thanks MM, I had a feeling the answer was going to be something like that. What is now the fail-over used to be live so we did create reports on there then copy them across.
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply