SQL 2005 on a Terminal Server?

[Guest bo_dong@yahoo.com]

Can I install SQL Server 2005 Enterprise Edition with Reporting

Services and Analysis Services on a Windows Server 2003 R2 Enterprise

Edition with Terminal Services?

 

I also installed IIS and volume lincensed Office 2007 on the terminal

server. Then users can remote into the terminal server and interact

with sql data using locally installed Access and consume sql reports

using local website. When I turn off remote connection to the sql

server, then the data is only accessible and visible to users who are

in the remote session.

 

Will this plan work? Anything special during install and setup?

 

Thanks

[Guest Vera Noest [MVP]]

Re: SQL 2005 on a Terminal Server?

 

It's tecnically possible, yes, but *not* recommended.

SQL and TS servers are tuned differently, since they perform very

different tasks (background versus foreground processes). Be prepared

for performance problems in both TS and SQL, if you have more than a

few connecting users. This also depends on your hardware, of course.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

bo_dong@yahoo.com wrote on 26 aug 2007 in

microsoft.public.windows.terminal_services:

> Can I install SQL Server 2005 Enterprise Edition with Reporting

> Services and Analysis Services on a Windows Server 2003 R2

> Enterprise Edition with Terminal Services?

>

> I also installed IIS and volume lincensed Office 2007 on the

> terminal server. Then users can remote into the terminal server

> and interact with sql data using locally installed Access and

> consume sql reports using local website. When I turn off remote

> connection to the sql server, then the data is only accessible

> and visible to users who are in the remote session.

>

> Will this plan work? Anything special during install and setup?

>

> Thanks

[Guest bo_dong@yahoo.com]

Re: SQL 2005 on a Terminal Server?

 

Vera,

 

Thank you for your reply. Can I put domain controller on a terminal

server as well?

 

Thanks.

[Guest Helge Klein]

Re: SQL 2005 on a Terminal Server?

 

Well, you _can_, but it is by no means recommended. I would use such

setups for test environments only.

 

Helge

 

On 27 Aug., 22:13, bo_d...@yahoo.com wrote:

> Vera,

>

> Thank you for your reply. Can I put domain controller on a terminal

> server as well?

>

> Thanks.

[Guest Jeff Pitsch]

Re: SQL 2005 on a Terminal Server?

 

Keep in mind that by doing this you are limiting the amount of users you

will get on the servers. Terminal Services and SQL are yin and yang to

each other on the same server. Each will try to consume as much

resources as they can. They will constantly be battling each other for

those resources. Adding the DC role onto the server will not help

matters at all. You are going to have severe performance issues by

going down this road.

 

Jeff Pitsch

Microsoft MVP - Terminal Server

Citrix Technology Professional

Provision Networks VIP

 

Forums not enough?

Get support from the experts at your business

http://jeffpitschconsulting.com

 

bo_dong@yahoo.com wrote:

> Vera,

>

> Thank you for your reply. Can I put domain controller on a terminal

> server as well?

>

> Thanks.

>

[Guest TP]

Re: SQL 2005 on a Terminal Server?

 

Yes, you can run TS, SQL 2005, domain controller, IIS and more

all on a single server without problems. Before doing this you

need to understand each application and the load it places as well

as the security and administration implications.

 

Running all of the above on a single machine *may* or *may not*

make sense in your specific case. Only you know your exact

requirements.

 

-TP

 

bo_dong@yahoo.com wrote:

> Vera,

>

> Thank you for your reply. Can I put domain controller on a terminal

> server as well?

>

> Thanks.

[Guest TP]

Re: SQL 2005 on a Terminal Server?

 

Hi Jeff,

 

I agree it is *possible* to have performance issues, but it is far

from a certainty. An app that uses SQL Server with tuned

queries can support a substantial number of users with minimal

CPU utilization, and acceptable RAM use. If the TS users

are *not* running applications that constantly peg the CPU

then the fact that SQL Server is running as well will have little

impact on their perceived experience.

 

Of course, each situation is unique. If the SQL Server application

requires large amounts of CPU, RAM, and disk I/O then it

would be a bad idea to run it alongside TS.

 

-TP

 

Jeff Pitsch wrote:

> Keep in mind that by doing this you are limiting the amount of users

> you will get on the servers. Terminal Services and SQL are yin and

> yang to each other on the same server. Each will try to consume as

> much resources as they can. They will constantly be battling each

> other for those resources. Adding the DC role onto the server will

> not help matters at all. You are going to have severe performance

> issues by going down this road.

>

> Jeff Pitsch

> Microsoft MVP - Terminal Server

> Citrix Technology Professional

> Provision Networks VIP

>

> Forums not enough?

> Get support from the experts at your business

> http://jeffpitschconsulting.com