February 6, 2008 at 1:04 pm
I have a ML 370 with 4 GB mem and 1 TB of disk space. I will be running SQL 2005 with Terminal server for a custom application. My question is: are there any known issues with running SQL and Terminal Server on the same box?
February 7, 2008 at 12:16 pm
Well you can do it, but the biggest thing that i have personally seen with putting both on the same box is the hit in performance. Since both SQL and terminal services are both very big resource hogs. That would be the only concern that i would have. Now if you have a low use SQL database or not a whole lot of users using the terminal services it probably would not be as noticeable, but that issue will still be there.
February 8, 2008 at 2:49 am
I hope you are running in 64-bit mode. 4GB is not a lot of memory, and adding more could do a lot for your performance.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
February 8, 2008 at 5:22 am
Yes it is a 64 Bit system w/4GB RAM. I will have about 8-34 users using the system. Also, regarding raid configuration:
* Is it better to do a 4-disk RAID 1+0 for each data file or a 5-disk RAID-5
* Should the database files be on their own array?
Thanks
February 8, 2008 at 7:03 am
If my experience is any indication, you will want to have separate machines for the SQL server and Terminal Server. All of our overseas users, and many of our domestic users, use termianl server to access the apps I support. We've had cases where 4 users manage to max out the processors on a termianl server. If that happens on a box that is a SQL server and a termianl server, the SQL perforamnce will take a huge hit. Boxes are cheap - use 2, one for terminal server the other for SQL.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply