Jez <Jez@discussions.microsoft.com> wrote:
> any pitfalls on running an SQL db on a terminal server?
> want to run MSTS with ms office and then sql client and sql db
> ?
Ideally, your terminal server shouldn't do anything else on the network -
shouldn't be a DC, a SQL server, file server, or anything. Just a big fat
shared workstation. This is for reasons of security as well as resource
load.
not planning to make it a DC or a file server. Space and cost confinements
have bought me here!
"Lanwench [MVP - Exchange]" wrote:
> Jez <Jez@discussions.microsoft.com> wrote:
> > any pitfalls on running an SQL db on a terminal server?
> > want to run MSTS with ms office and then sql client and sql db
> > ?
>
> Ideally, your terminal server shouldn't do anything else on the network -
> shouldn't be a DC, a SQL server, file server, or anything. Just a big fat
> shared workstation. This is for reasons of security as well as resource
> load.
>
>
>
Sql server can co-exists with TS on the same box. Like Lanwench and Hank
Arnold suggested, if you start seeing performance issues when many users
accessing both at the same time, it may not be a bad idea to separate them.
Thanks
Soo Kuan
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jez" <Jez@discussions.microsoft.com> wrote in message
news:473DF3DC-D012-43D4-92BA-A35C6D3FF2AE@microsoft.com...
> any pitfalls on running an SQL db on a terminal server?
> want to run MSTS with ms office and then sql client and sql db
> ?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.