Home/ Questions/Q 7014225
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T22:29:38+00:00

I’m developing an application which queries data from the host, and then inserts them

  • 0

I’m developing an application which queries data from the host, and then inserts them into an SQL database. My application runs in random times on our PC’s ( we have 600-700 PCs ) from a server location, so my application isn’t located at all PC. It is only located at the server. So it is possible that sometimes it runs on 50 PCs.

I keep getting two types of SQL error messages. The first is time out, and the other is SSL security error. Right now my application executes about 5-10 SQL commands. So i’m thinking to rewrite my code to call stored procedures which could reduce the number of SQL calls. The only question is that is it worth it? I mean of course, it has its advantages, because if i have to change something then it is enough to change the stored procedure, and i don’t have to recompile my application. But won’t that cause trouble for the SQL server? I mean isn’t that a problem when the same stored procedure will be executed 50 times at the same time?

So what way is better? Using stored procedures, or using SQL commands in my code?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you often call several identical SQL statements in a row, the answer is clear-cut: use SPs to reduce the number of round trips. The load on your SQL server is not going to change, but the network latency will go down due to reduced number of round-trips. As an added bonus, your system architecture may become easier to understand and maintain, because the complex SQL logic would be encapsulated in your data access layer.

    This may not have anything to do with your SSL errors, but the situation with timeouts has a decent chance of improving.

    • 0