Search faster in Huge database

Question

1.00/5 (2 votes)

See more:

SQL-Server-2005

, +

Hi Guys,

Please assist me how to make my web application faster in huge database records.

I have database having huge records approx 30Lacs records and we are facing speed issue while inserting/updating and SEARCHING. We already implemented normalization,indexes, full text search in SQLSERVER2005/2008 and AjAX, javascript in web.

Please let me know how we can improve the speed of application. Also is there any way in SQLServer2005/2008 to make it faster search/insert/delete operation through web application.

Please also suggest about Partition. Is it helpful to implement over 30lacs records? OR It is not advisable to do that. I do not have idea on partition. Please also comment.

Waiting for your reply...

Thanks in advance.

Posted 29-Apr-13 2:52am

Freelancers

Updated 29-Apr-13 4:09am

v2

Add a Solution

Comments

Ankur^\m/ 29-Apr-13 9:11am

1st thing would be to check out the query plan of your queries. You say you have everything in place but it is still slow. It seems your indexes are not well designed. Query plan will help you a lot. You may also need to rebuild your indexes based on latest statistics.

[no name] 29-Apr-13 10:31am

I think first step should be to identify the exact issue..Is it DB related for sure ? I came across such issue once and found out that one of the third party control was sending multiple requests to the server which was delaying the CRUD..Try using fiddler for traffic and If you eliminate those issues you can go ahead with OP's suggestions.

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)