422,734 Members | 1,335 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 422,734 IT Pros & Developers. It's quick & easy.

SQL Server slow response

P: 1
HI,
I have developed a project for a trading Company using C# 2.0 and SQL Server 2008R2.
My project is working properly. No issue regarding the code.

But I am worried about one thing.

Daily so many records are inserted, around 5000 above records are entered in different tables per a day.

hard disk size is 1TB.

I Think after few days there will be a million of records, then will my Software work slow? or it will work as it is now.

If it will work slow then what will be the remedy.
[I implement Primary key index in some tables.
Give me any other solution].

[Network connection is not the issue.]

Please answer me.
Thanks in advance.
hari
Dec 5 '17 #1

✓ answered by Frinavale

Usually database engines are pretty quick at retrieving data.

Especially if you have indexed them correctly.

However, if you are experiencing slowness in retrieving information then you should take another look at your queries to make sure they are optimized. Sometimes, if your query involves a lot of joins and other look-ups, it is better to rearrange them or restructure them to select smaller subsets and then do further computations on these instead.

You could also use stored procedures which are per-compiled and optimized by the database engine. This saves you a little bit of time; but in the bigger picture, make sure you have indexed your tables correctly and that your queries are optimized for your searches.

Occasionally you should consider compressing and reindexing the database.

Also, you could consider archiving old data and clearing your database to make your base smaller (you may also need to do this to offload some data to keep your size within the limitations you have). This may or may not be a realistic option depending on your system requirements.

Share this Question
Share on Google+
1 Reply


Frinavale
Expert Mod 5K+
P: 9,731
Usually database engines are pretty quick at retrieving data.

Especially if you have indexed them correctly.

However, if you are experiencing slowness in retrieving information then you should take another look at your queries to make sure they are optimized. Sometimes, if your query involves a lot of joins and other look-ups, it is better to rearrange them or restructure them to select smaller subsets and then do further computations on these instead.

You could also use stored procedures which are per-compiled and optimized by the database engine. This saves you a little bit of time; but in the bigger picture, make sure you have indexed your tables correctly and that your queries are optimized for your searches.

Occasionally you should consider compressing and reindexing the database.

Also, you could consider archiving old data and clearing your database to make your base smaller (you may also need to do this to offload some data to keep your size within the limitations you have). This may or may not be a realistic option depending on your system requirements.
Dec 5 '17 #2

Post your reply

Sign in to post your reply or Sign up for a free account.