Join or sign in Register for your free TechRepublic membership or if you are already a member, sign in using your preferred method below. Use Your Email Use FacebookUse Linkedin

SQL Server -MS Access with Terminal Services (20-30) Users

Locked

I’m trying to determine if one machine can handle the following configuration of MS-SQL Server 2003 using ODBC to connect with client MS-Access for input/reporting. At the same time, there are 20-30 users who use terminal services at the same time.

Does anyone have experience with this architectural configuration in terms of impact on performance?

Topic

Clarifications

In reply to SQL Server -MS Access with Terminal Services (20-30) Users

Clarifications

In general, that does not sound too strenuous

In reply to SQL Server -MS Access with Terminal Services (20-30) Users

How many concurrent SQL users, and how intensive is the database access?

Are the TS users all on the local LAN?

What type of app is running under TS?

In general TS is very bandwidth-efficient since it’s generally run over a slow WAN or VPN connection.

The two concerns I see would be if the SQL database is something very I/O intensive with huge tables and a lot of complexity, then the server would need sufficient RAM and processor to handle that.

The other issue would be if the database or TS applications had very strict latency expectations/requirements. Then it may be necessary to implement QOS and also engineer the LAN to meet your throughput/latency requirements.

[Author]

Replies