We've been using SSRS for years with AR System. Although we don't use the ARODBC driver, I don't see any reason why you couldn't--we just chose not to so we don't have to worry about Remedy permissions affecting our report content. Our report access is controlled via Windows authentication and roles so we don't need our reports filtering data based on Remedy permissions. You will want to set up a read-only login within the database to use with your report connection.
We used SSRS version 2000 (AR v6x) and are now running v2005 against AR v7x without any problems. We just use the standard SQL connection. If you are making a direct connection to the database and pulling report data, how can it not be "compatible"? What they are probably telling you is they do not provide support for it so you are on your own. Personally, it's a very easy product to use, has real nice flexibility and capability especially considering it is free with your SQL Server license. We use it both on the web and on the back-end via direct URL calls and usually render the reports automatically in PDF or Excel format. You can also have the report come up in the reporting interface for them to enter/select parameters. There is only one instance where we use Crystal Reports and that is where we need fully-justified text which SSRS does not yet support. Since it is a User Tool report, the included Crystal DLL supports that. Everywhere else (over 150 reports) is all SSRS. One thing you will need to do if you do not use the ARODBC driver is to create a set of functions for date conversions, etc. We have a set we developed to go back and forth between integer and various date formats. You will also need to convert any attribute menus and status fields to their clear-text values. We do some of that within the report query (SQL statement) and some within the reports using IIF. We've also stressed the use of character menus versus attribute menus in all new development to simplify report delivery. I recommend you use the ARODBC driver initially because it is less work and you don't need to perform all of the extra conversions within SQL, the report, or using functions/stored procedures. We did use the ARODBC driver initially and it did work. //SIGNED// Craig Carter Supervisor, IT Specialist, RSP -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Raj Kiran Sent: Tuesday, July 28, 2009 10:29 PM To: arslist@ARSLIST.ORG Subject: Re: SSRS AR ODBC Compatibility ** I remember during my last project, I contacted BMC regarding the compatibility of SSRS with AR System and was told that SSRS is not compatible with Remedy AR System. Could anybody please confirm this? Thanks, Raj On Tue, Jul 28, 2009 at 10:50 PM, shweta kumar <shweta_kuma...@yahoo.com> wrote: ** Has anyone done SQL Server Reporting using AR ODBC? Is SSRS comaptible with AR ODBC? Thanks Shweta _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
