Additionally, since you are already using SQL Server 2005 Enterprise, have you considered SQL Server Reporting Services? We use it almost exclusively for everything and reports can be rendered via a URL, through the RS ASP interface, or through your own interface that calls the underlying report service.
Craig Carter -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Axton Sent: Thursday, January 26, 2012 12:39 PM To: [email protected] Subject: Re: Need to build a reporting server I would like to ask, "Why do you want a Remedy server for reporting purposes?" Remedy is not very good at reporting. There are tools out there that are good at reporting (no bias) such as Business Objects. The things Remedy and these reporting solutions have in common is a database server. Both need one. To remove contention on the database between the Remedy server and reporting system, you should consider a seperate database server. There are many methods to get the data from the Remedy database to the reporting database, each with it's own set of benefits and limitations. Axton Grams On Thu, Jan 26, 2012 at 12:54 PM, patchsk <[email protected]> wrote: > ** > > 1. If i want to setup a reporting server, then shall i need new hardware? > --> There is an option where you can install multiple instances of > --> remedy in > a single server but not many people use that. > Better to have a separate hardware for this or atleast have a new > virtual machine. > 2.Shall i need to install the remedy software in it? > -->If you want to use just for reporting without need to see remedy > -->screens > then all you need is a new database. > However if you want users to query this new instance like they do > in production then you do need to install remedy also. > 3. Will it consume remedy license? > --> Yes you do need a new arserver license as well as fixed and > -->floating > licenses depending on the type of users for this new instance. But > with the new license policy you can install as many arserver licenses > as you want without buying extra arserver licenses. But you need to > buy floating licenses if you want. The fixed licenses from production > can be used in the reporting if it is for the same users. > However you first need to be converted to the new licensing method. > Best options is to check with your BMC account manager who will guide > you in the correct direction. > 4. Shall i need to install the databse and need to synchronize with > the production database? > --> Database level synchronize may not work because if you delete the > --> old > records from production then they get deleted from reporting also. > You can use remedy DSO or aie to transfer data from prod to reporting. > 5. > No matter how you do since both the environments are different the > users have to click a button or something to get the login screen for > the reporting instance and report from there. They just can't use > production env and report from reporting env transparently. However if > you use single sign on then the user will be logged in automatically, > they just have to enter the reporting criteria and click search. > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
