March 13, 2008 at 1:54 pm
Hey all,
First I want to say that I have learned a lot from SQLServerCentral and the forums. I'm a non-DBA just learning SQL and SSRS working with 2 other guys in house to replace a legacy system with SQL Server 2005 and SSRS. Between the 3 of us we might make for 1 good DBA!! 😀 SQLServerCentral rocks!
Now I need some more shared expertise. We currently have our development environment all on 1 box -- SQL 2005, SSRS 2005, and IIS. Its an OK machine -- Windows Server 2003, dual Xeon processors, 3GB RAM, and large SATA drives (with RAID).
Our database is currently around 3GB but I expect it will increase by 25-30% before we are done. The ReportServer db is around 250MB and I have around 100 more reports on my to-do list. It will serve a our manufacturing and warehousing needs. I don't expect to have many insert/update/delete transactions on a daily basis. We love to run reports around here so I imagine managers will be running reports frequently (maybe 10 users or so).
Can we keep everything on 1 server and be OK? Or should we keep SQL and SSRS separate?
One idea we have kicked around is to have 2 boxes (1 for SQL and 1 for SSRS) and replicate the "live" database from the SQL server to the SSRS server--then run all reports from the replicated copy. Is that an advisable scenario?
Also, does anyone have a recommendation as to server hardware for SSRS??
Any suggestions would be greatly appreciated!
Thanks,
Ron
April 2, 2008 at 11:15 am
It is something that my company is considering too. Is it true that we need 2 license of SQL Server 2005 to do this setup (one for each box)? I would apreciate any inputs on this setup and how it would optimize the report processing.
Thanks 🙂
April 2, 2008 at 11:50 am
Guts N Glory (4/2/2008)
It is something that my company is considering too. Is it true that we need 2 license of SQL Server 2005 to do this setup (one for each box)? I would apreciate any inputs on this setup and how it would optimize the report processing.Thanks 🙂
True as to the licensing. If you want to install any component of SQL server on a box, that box needs to be "appropriately licensed". So in this case - you'd have to license the 2 servers separately.
Replication is certainly a possibility. Of course - if you're reporting on largely static data (or if it's a static snapshot), then you might also care to preprocess your "hot" reports. Why regenerate them from scratch if they're not going to change for the day.
I mean - why rebuild a large matrix summary report 400 times if it's going to be the SAME all day? Create the cross tab after the nightly snapshot in a static table, and report off of the static table.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply