• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Performance Management Lawson Business Intelligence/Reporting/Crystal

Repository Database

 3 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
hrasmuss
New Member Send Private Message
Posts: 0
New Member
9/19/2007 5:55 PM
Does anyone have a recommendation for the setup of the Repository Database used with LBI. Our Lawson databases exist on a remote Sun Solaris box seperate from the Lawson application box. Do we have to use Oracle as our repository database? Does it have to be on the same box as the Lawson database? Or, could we use SQL Server as the repository database and the OLAP Analysis and place it on the LBI box?
Chris Martin
Veteran Member Send Private Message
Posts: 277
Veteran Member
9/19/2007 6:06 PM
You can use either Oracle, SQL Server, or DB2 for your repository. As long as the LBI server has connectivity with the database, the database can reside wherever you want it to (ie Oracle on Unix or Windows box, SQL on a Windows box, etc). My preference is for the repository to not reside on the LBI server (for resource consumption reasons), however it will usually do just fine installed on the same box. I've found that RAS is a bigger area of concern from a resource perspective than the database.
hrasmuss
New Member Send Private Message
Posts: 0
New Member
9/19/2007 6:11 PM
Thanks Chris! So how about this scenario...
Lawson Oracle Database on Sun Server
Lawson Applications on AIX Server
LBI Repository SQL Database on Window Server
LBI Modules on same Windows Server
SQL OLAP cubes on same Windows Server
Crystal RAS on same Windows Server

Do you think this would work or not? Thanks!
Chris Martin
Veteran Member Send Private Message
Posts: 277
Veteran Member
9/19/2007 6:44 PM
Depending on the number and type (ie scheduled vs ondemand) of reports you have, that should work. If you run into any server resource issues, you may want to consider moving RAS off to a dedicated server. Smart Notes can be resource intensive as well, but it looks like you're not implementing that.