Hello,
I have an application that converts one database to another. This application has multipule threads all inserting diffrent data into the new database. The code works for a number of inserts ranging between 24 and 120 but then fails with the error:
There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.
As far as I can see this isn't a coding issue as all it is doing is inserting null in to all fields in a table and the code is exactly the same each time it executes, and it executes fine a number of times before it fails. For this reason I have to look at Sql Server and ask if there is any other reason why it would produce this error apart from the obvious?
The application creates a new connection each time it does an insert and then closes the connection once it has finished. As a result the application puts alot of pressure on the sql server and will use 100% of the sql servers processing power along with most of the ram. Is this error produced when sql server can't handle a query for some reason?
Any ideas would be welcome as I have spent three days on this and got no where!
If knowlege can create problems it is not through ignorance that we will solve them.
Isaac Asimov
I have an application that converts one database to another. This application has multipule threads all inserting diffrent data into the new database. The code works for a number of inserts ranging between 24 and 120 but then fails with the error:
There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.
As far as I can see this isn't a coding issue as all it is doing is inserting null in to all fields in a table and the code is exactly the same each time it executes, and it executes fine a number of times before it fails. For this reason I have to look at Sql Server and ask if there is any other reason why it would produce this error apart from the obvious?
The application creates a new connection each time it does an insert and then closes the connection once it has finished. As a result the application puts alot of pressure on the sql server and will use 100% of the sql servers processing power along with most of the ram. Is this error produced when sql server can't handle a query for some reason?
Any ideas would be welcome as I have spent three days on this and got no where!
If knowlege can create problems it is not through ignorance that we will solve them.
Isaac Asimov