.NET Application running on Terminal Server

I'm new to coding .NET using c#. I have previously written a couple of simple .NET applications running on desktops. I will now have to write a new application running on Terminal Server with between 25-50 concurrent users. The current specs call for using SQL Server Express to start with and maybe upgrading to the full SQL Server version at some point. I have a two part question:

1. Other than the memory usage of multiple Users on the server, is there anything else that I need to be concerned about regarding running a .NET application on Terminal Server?

2. I understand the limitations of SQL Server Express. Basically I will connect/disconnect when reading/writing to the database and not keep the connection open, so I should be able to toggle among the Users since i have only 5 CALS. Is there anything else, generally speaking, that I should be concerned about regarding Express?

I understand that these question are a little general. I haven't started coding yet and I'm trying to get a handle on possible pitfalls, issues, etc.

Thanks in advance for all your help!
MikeNY1Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jacques Bourgeois (James Burger)PresidentCommented:
You have to be aware that the connection to the database is not closed immediately when you call Close in your code (https://msdn.microsoft.com/en-us/library/8xx3tyca%28v=vs.110%29.aspx).

However, the limitation on SQL Server Express is not the number of connections. It used to be the number of concurrent transactions, that is you could not run more than a given number of commands at the same time. But even that has disappeared from the specifications of the more current versions.

The limits are now more something of the capacity, such as the size of the database, the number of processors that it can use, the amount of memory that it uses, the tools that you can use with it. You cannot debug your stored procedures for instance.

Here are the specs in comparison with higher versions for 2014: https://msdn.microsoft.com/library/cc645993.aspx

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Vitor MontalvãoMSSQL Senior EngineerCommented:
Looks like Jacques gave a very good answer.
MikeNY1, do you still need any more inputs from us?
MikeNY1Author Commented:
Thank you for your response. Yes, this answered my questions and it was very helpful in getting me off on the right foot with my design of the project.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.