Timeout error while inserting the records in database.

Question

1.00/5 (1 vote)

See more:

Hi,

I have a big problem while inserting the records in database.
In my job table I have 20 laks of records. When I inserting the new record first I will check based on some fields(like url, location..etc) if the record is exist or not.
Each and Every field check 17 laks of records before inserting. Now I got timeout error while inserting the records. Now the records are increased daily.
My server configurations is 32 gb ram and 2 TG harddisk.

Please give me the suggestions.
Thank you....

Posted 21-May-14 20:42pm

NagaRaju Pesarlanka

Add a Solution

Comments

Maciej Los 22-May-14 2:47am

And what have you tried till now?

NagaRaju Pesarlanka 22-May-14 2:48am

try to find the solution.

Bh@gyesh 22-May-14 2:50am

Try to increase "ConnectionTimeout in web.config. If it is not working then, try to increase commandTimeout in command property.

Kornfeld Eliyahu Peter 22-May-14 2:57am

Why to check existence with code - use SQL fro that (index, foreign key, constrains)

NagaRaju Pesarlanka 22-May-14 3:00am

Please give one example link or code.

manvendra patel 22-May-14 2:58am

try this in connection string -Connect Timeout=3000;pooling='true'; Max Pool Size=3000;

Sunasara Imdadhusen 22-May-14 3:17am

Where is your code

seeshil 22-May-14 5:10am

Increasing the connection Timeout may work but question is how you are searching through these many records and why you want to do this???

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)

Bernhard Hiller · Answer 1 · 2014-05-21T21:29:00

Add an additional unique constraint to your table, such that fields which you check for duplicates are guaranteed to be unique by SQL Server already.
You can set constraints e.g. with SQL Server Management Studio (click on the table - then Constraints - then "New Constraint").
An index could do so, too.