Performance impact of Terminal Server on SQL Server

Hello,
We have a Windows 2000 Server box with SQL Server 7.0
installed. The database is maintained by a vendor, but
many customizations (other DBs) are built and maintained
on the same server by us (that's SQLServer={VendorDB1,
VendorDB2,...VendorDBN, OurDB1, OurDB2,...OurDBN}). We
desire to be able to manage the server (of the box, not
SQL Server) remotely via Terminal Server but our vendor
insists against it saying that it will adversely affect
the performance of the database. We do this with other
SQL Server boxes and have not noticed any significant
degradations in performance.
I've noticed the following: if I go to a Win2K Server box
running SQL Server and initiate a terminal server session
*away* from the box (to another machine), the SQL Server
performance drops significantly. However, if I am at a
remote machine and initiate a terminal server session
*to* a box running SQL Server, I experience no
performance problem(s).
Given the above, can anyone point me to any documentation
detailing performance issues related to Terminal Server
and SQL Server on the same machine? Can anyone clarify
the problem for me? That is, is it the case the SQL
Server performance will degrade if Terminal Server is
running *regardless* of whether you are connecting from
the box or to the box?
Thanks!
Quentinone connection into the sql server box for management and
administration should not be a big deal,
i would not run multiple terminal server sessions into a
heavily loaded sql server,
try running perfmon on the terminal server including the
context switches/sec counter.
open one session, run notepad and start typing a normal
rate.
each terminal server session will incur that amount of
load. at some point, the context switching rate will be
high enough to completely disrupt sql server,
but session for administrative purposes only is not bad,
>--Original Message--
>Hello,
>We have a Windows 2000 Server box with SQL Server 7.0
>installed. The database is maintained by a vendor, but
>many customizations (other DBs) are built and maintained
>on the same server by us (that's SQLServer={VendorDB1,
>VendorDB2,...VendorDBN, OurDB1, OurDB2,...OurDBN}). We
>desire to be able to manage the server (of the box, not
>SQL Server) remotely via Terminal Server but our vendor
>insists against it saying that it will adversely affect
>the performance of the database. We do this with other
>SQL Server boxes and have not noticed any significant
>degradations in performance.
>I've noticed the following: if I go to a Win2K Server box
>running SQL Server and initiate a terminal server session
>*away* from the box (to another machine), the SQL Server
>performance drops significantly. However, if I am at a
>remote machine and initiate a terminal server session
>*to* a box running SQL Server, I experience no
>performance problem(s).
>Given the above, can anyone point me to any documentation
>detailing performance issues related to Terminal Server
>and SQL Server on the same machine? Can anyone clarify
>the problem for me? That is, is it the case the SQL
>Server performance will degrade if Terminal Server is
>running *regardless* of whether you are connecting from
>the box or to the box?
>Thanks!
>Quentin
>.
>sql