Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Installation Windows Server 2003

Status
Not open for further replies.

Auguy

Programmer
May 1, 2004
1,206
US
I'm somewhat confused as to what I have to install and on what machines. The client has a Windows Server 2003 that has SQL2000 and IIS running on it and a workstation with VS 2003 installed. Am I correct in assuming that I only have to install the server components on the server and the client components on the workstation? This is a small client so I am not too worried about performance with SQL and the report server on the same box. Any other suggestions or hints would be appreciated.

Auguy
 
Are you talking SQL Server in general or reporting services specifically?



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
Reporting Services 2000 only, SQL 2000 is already up and running on the 2003 server. The reason I ask is that my development machine in my office is XP Pro with both SQL and reporting services installed.

Auguy
 
If you're installing SRS on a server, I recommend only the Report Manager / Reporting Services DBs be installed on there.

Client tools, such as Report Designer, etc. should be installed on the client machines. There is, so far as I know, no reason to install that functionality on the actual server. And give that you already have IIS and SQL on the same server (FYI: this is a security risk), I would keep as many extraneous tools off the server as possible.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
Thanks for the info, it confirms what I thought.

Auguy
 
NP. Glad I could help.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
Ok, Everything installed in the server (Small Business Server 2003) but I couldn't install the client tools on the workstation. I have the Hitchhiker's Guide to SQL Server 2000 Reporting Services book which I used as a guide. To install the client tools on the workstation, the book tells me to enter the SQL cd key and the book tells where to find the key in the registry. I entered the SQL key (the one from the server) but it tells me it an invalid key. There is no SQL installed on workstation, only on the network. Do I need some version of SQL installed on the workstation to install the tools or am I missing something?

Auguy
 
You do need some version, even if it's just the developer edition, of SQL installed on each box that uses SRS or the client tools. If you don't, Microsoft wants a separate license for SRS.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
NP. Glad I could help.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top