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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-02-03 : 08:14:27
|
| Merlin writes "I watched the webcast launch and was eager to start using the Reporting Services add-in. But after reading the online docs at the Microsoft website, and perusing their newsgroups, there seems to be several gotchas in the fine print. One deployment option is to put all RS components on an existing SQL box. That would require RS, IIS and the user SQL databases all on a single box. So Free RS, but...security and performance concerns. Alternatively, you could deploy some RS components to a separete server; e.g., a web server. The catch there is you'd have to purchase another SQL license. That can be expensive depending on # or procs, which edition and your licensing scheme. My questions: a) Does my interpretation of the deployment / licensing options sound correct?b) Any comments on the security and performance aspects of putting IIS, RS and SQL user databases all on a single box? In my case, concurrent users of the SQL user dbs varies anywhere from 5-100. It's a newer dual proc SQL 2K on Win2K Server. Someone suggested IIS6 that comes with Server 2003 Server might make the single box option less onerous." |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-02-03 : 12:26:23
|
| You don't need a separate license for RS in your alternative example. SQL Server should be on a dedicated server. Whichever components do not need to be on a SQL Server machine, move those to the web server.Tara |
 |
|
|
|
|
|
Reporting Services Licencing and Deployment