The query has been canceled because the estimated cost of this query

Question

Post reply

The query has been canceled because the estimated cost of this query

Anuj Rathi

Say Hey Kid

Points: 703
More actions
January 25, 2013 at 8:56 pm

#269736

Hi Experts,
I am getting below error while executing the stored procedure.
The query has been canceled because the estimated cost of this query (3258) exceeds the configured threshold of 2500. Contact the system administrator.
I am importing the XML into the table. Actually, I am uploading CSV contacts in my application & then push the XML to sql server. Here, I extract the contacts using xpath query, & save into a table. In my local machine, this code works fine while I upload this code on production server, it raises the above error. below is the sample code which I am using:
INSERT INTO @TempTable(FullName, FirstName, LastName, Email, DateOfBirth, CountryCode)
SELECT FullName = T.Item.query('fullname').value('.', 'VARCHAR(256)'),
FirstName = T.Item.query('firstname').value('.', 'VARCHAR(256)'),
LastName = T.Item.query('lastname').value('.', 'VARCHAR(256)'),
Email = T.Item.query('email').value('.', 'VARCHAR(256)'),
DOB = CASE WHEN T.Item.query('dateofbirth').value('.', 'VARCHAR(10)') = '' THEN NULL
ELSE CONVERT(DATE, T.Item.query('dateofbirth').value('.', 'VARCHAR(10)'), 103)
END,
CC = T.Item.query('country').value('.', 'CHAR(2)')
FROM @xmlData.nodes('contacts/contact') AS T(Item);
above code works fine & takes only few milliseconds on my local system but throws an error on production server.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Anuj Rathi Say Hey Kid Points: 703 More actions · Answer 1

I have found a solution. I also want to share with you guys.

http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/31f80c1f-6285-4966-b7ed-9d0f93816f52

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 2

Anuj Rathi (1/26/2013)
I have found a solution. I also want to share with you guys.
http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/31f80c1f-6285-4966-b7ed-9d0f93816f52

Making it a hot link:

http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/31f80c1f-6285-4966-b7ed-9d0f93816f52

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 3

Anuj Rathi (1/26/2013)
I have found a solution. I also want to share with you guys.
http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/31f80c1f-6285-4966-b7ed-9d0f93816f52

Whoa! Thank you very much for posting the solution and it's real nice that a person on that thread recommended creating some XML indexes, but in the name of Codd and all that is holy in the world of databases, let's back the database truck up a couple of miles.

Ok... let's ask a question here. How many people think that storing a CSV column of data in a database is a good idea? 😉 Even if you could index it, would it be a good idea?

I certainly hope no one thinks so. So why do people allow what turns out to be some highly denormalized data with HUGE and (many times) unnecessary delimiters that will screw up their online indexing because of the blob content to be stored in their databases???

Forget about the XML indexes. Normalize the data and store it in the database correctly!

{EDIT} Yeah, yeah... I know 2012 overcomes the blob-content problem with rebuilding indexes online. What's been the excuse since 2000 came out? That doesn't change the fact that XML is one of the most horribly bloated, pipe clogging, disk hogging, memory eating, denormalized methods of communication ever devised (Heh... man, it was hard to keep THAT clean:-D). 😛

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Anuj Rathi Say Hey Kid Points: 703 More actions · Answer 4

Hi Jeff,

You are right. This is not good to save CSV in database. I also don't save xml data into database.

I think Sathya (who proposed that solution) was thinking that I save my CSV in database & this is the query to fetch records.

But this is not the case. Actually, I have to import contacts CSV in my web application. Here I convert this CSV contacts into XML & pass this XML to database as XML data type.

Here @xmlData is the variable which receives input data in my stored procedure. then I extract data with the help of XQuery & save into my table.