Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
MorrisK
Yak Posting Veteran
83 Posts |
 Posted - 2006-11-01 : 16:51:40
|
| I'm new to IIS, Reporting Services, and Analysis Services and am considering installing them all on our production SQL Server box. This instance of SQL Server also holds the database for our OLTP system.Our plan is to only allow access through our intranet.Any warnings, comments, or suggestions? Kevin |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2006-11-02 : 11:01:15
|
well best practices usually don't reccomend that, but i guess it depends on your situation.Will the server be accesible from the internet, how trusted are your users, etc...if you provide more info we might be able to help better.Go with the flow & have fun! Else fight the flow  blog thingie: http://weblogs.sqlteam.com/mladenp |
 |
|
|
Will Riley
Starting Member
10 Posts |
Posted - 2006-11-03 : 05:57:12
|
| As spirit says, it really depends on your circumstances. The configuration you talk about would be referred to as "All in One" and is certainly do-able. It would usually only be seen in a small company though and is appealing for the cost conscious :)Normally you'd see it split so that you have a SQL Server which holds your RDBMS, along with Analysis Services, Integration Services etc and a second Reporting Server running Reporting Services & maybe Sharepoint or some such thing. Your clients only then require internet browser etc...You may also need to split off the Analysis server from your RDBMS if it is not allowed much downtimeCheers,Will |
|
|
|
MorrisK
Yak Posting Veteran
83 Posts |
Posted - 2006-11-03 : 14:13:59
|
| Thanks for your input. I didn't think to mention more details. This is all being done with SQL Server 2000 with Windows 2003 Server.We are a small company and only internal users will be accessing the reports. For this reason we didn't setup SSL.Will - You are right. I'm doing it this way because of the cost. I'm looking at this as a way to prove the concept. If it proves to be beneficial, maybe money can be found someday to move it to another server.Would you mind elaborating on what you mean by "You may also need to split off the Analysis server from your RDBMS if it is not allowed much downtime"? Is this a potential problem?Thanks again,Kevin |
|
|
|
Will Riley
Starting Member
10 Posts |
Posted - 2006-11-03 : 16:37:21
|
Depends on a number of things such as:The size of your database - like what are you gong to be running on the SQL server? An OLTP snapshot for reporting, A Data Warehouse - are you going to build Analysis Services layer on top of all this for Cube reporting / MDX querying etc...If you are running a "live" OLTP database on the SQL Server, I would not recommend using that same server for reporting services as well or serious queris as you may seriously kill the response times for your users if you start running queries all over the live box.We used a simple single machine set up to prove the SQL 05 concept, but all we did was use a copy of the "live" database on the test server (which incidentally was a HP laptop with 1gb RAM & 40GB hard disk - so you can do this on a budget) - we also used the developer version of SQL 2005 as this is the equivalent of Enterprise but a fraction of the cost and OK if you are just proving the concept.FYI the database itself was only around 8GB, but the whole thing worked fine (if a little slowly ) Cheers,Will |
|
|
|
|
|
|
|
|
SQL Server, IIS, RS and AS all on one server