If we pull multiple tables from stored procedure instead of procedure per table, how it will affect Sql Server’s performance?
If we pull multiple tables from stored procedure instead of procedure per table, how
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If we pull multiple tables from stored procedure instead of procedure per table, how it will affect Sql Server’s performance?
In terms of the database engine itself and the load on it, it makes little difference.
In terms of network IO, it is normally better to do one big query than several small ones, as each connection takes some time to setup.
In general – pull in all the data you need in one batch instead of several if performance of the database and application are important.