Threads issue

Question

0.00/5 (No votes)

See more:

Hello,
I'v a following statement with which I'm creating 100 tables and inserting values into it respectively.

cmd1.ExecuteNonQuery();

But its throwing a error like "time out exception" and the above is not executing completely...

I think the .net compiler is executing the statement fastly where as it requires bit more time..

As per i'v to use Threads concept but not clear...
Can u help me to solve issue.

Posted 30-Jan-11 21:49pm

krishna kishore58

Add a Solution

Comments

Indivara 31-Jan-11 3:51am

Do you really have to do 100 tables in a single SQL statement?

Sergey Alexandrovich Kryukov 31-Jan-11 3:53am

Needs more detail explanation of the goals. Also, please perform the search on "thread" or "threading" in Answers -- I along gave many answers on the topic, other members too. After that, you could ask more defined question.
Thanks for understanding.
--SA

krishna kishore58 31-Jan-11 3:57am

yes I'v to do...

2 solutions

Solution 2

The time out exception is most likely to be waiting for a response from the SQL server (or whatever database you are using). I would strongly suggest reducing the number of tables and values you insert in a single command: this could take some considerable time and is probably outside the time out limits for your database system to respond. You could increase the limits with your database manager (google "increase timeout sql server" for information on how), but it would be better to look at converting your single monolithic command into a number of commands, possibly transacted so you can roll back in case of failure.

Posted 30-Jan-11 21:56pm

OriginalGriff

Comments

krishna kishore58 31-Jan-11 4:01am

thanks 4 replying...Ur r8 but the all the command structure to create 100 tables and to insert values are available in a file. And I'm taking the content of the file into string and then executing the string ...Hope u understand..

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)

Prerak Patel · Accepted Answer · 2011-01-30T21:55:00

Solution 1

You can set cmd1.CommandTimeout. You have to specify time in seconds.

By default it is 30 seconds. Your procedure may be taking longer than that.

I think, creating 100 tables won't take much time. But I don't know how much data you are adding to them! I think if you are not populating much data, try 300 as timeout. You can increase timeout if required.

Posted 30-Jan-11 21:55pm

Prerak Patel

Updated 30-Jan-11 22:31pm

v3

Comments

krishna kishore58 31-Jan-11 3:58am

But i donno how much time that statement requires...

Prerak Patel 31-Jan-11 4:01am

You can guess the expected time for execution, or you can split the queries.

Prerak Patel 31-Jan-11 4:02am

I think, creating 100 tables won't take much time. But I don't know how much data you are adding to them!

krishna kishore58 31-Jan-11 4:03am

I'm not writing all the queries manually. They r available in a file. And i'm copying the file content to string and executing that string...

Prerak Patel 31-Jan-11 4:06am

Then try the max you can imagine. I think if you are not populating much data, try 300 as timeout.

krishna kishore58 31-Jan-11 4:07am

Jus a min lemme check...

Prerak Patel 31-Jan-11 4:21am

You can increase timeout if required. If this helps, mark the answer.

krishna kishore58 31-Jan-11 4:23am

Hey dude its working.. thanks a lot...

Prerak Patel 31-Jan-11 4:25am

Glad to help. Mark it as answer then.