Is it right to have a single table for atleast 100 users to access every now and then

Question

1.00/5 (1 vote)

See more:

Hi,

I'm developing a small application in C#. Backend SQL Server 2012. It is a ticket generation module. The Ticket table consists of 61 columns. For Every ticket keyed in an entry is inserted in this table. As and when some changes are done to the ticket, such updates are also done in this table.

We will be having about 100 or more users simultaneously doing the ticketing.(The necessary Transaction looping etc., are in place).

My doubt is - is it correct to have many users update the same table. Will it not slow down the application?

I could not test it since, I do not have this kind of a setup. If Anyone here has an experience please suggest the right way.

Thank you.

What I have tried:

Haven't tried Anything. Searched in Google but could not get the right track.

Posted 20-Jan-19 20:45pm

Priya-Kiko

Updated 20-Jan-19 21:03pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2019-01-20T21:04:00

No, that's fine - it's what SQL Server is there for. How quick it will be depends on too many factors to just say "it will / won't run slow": the machine SQL server is running on, the bandwidth of the connection(s) to it, the size of the updates, the frequency of teh updates, other activity on the DB and / or network, ...

If it proves too slow in production, any of these things can be improved, right up to expanding SQL Server to a server farm to distribute the load.