A similar thing was happeing to one of my sql server.

The reason was that the sproc was reading from a huge heap table (no primary key - clustered idnex) a...

da-zero (5/14/2010)

---

andrew.ingram

---

Recently a number of users have asked whether it would be possible to browse the cubes on-line rather than using Excel as especially while...

the problem seems to be absolute path on different machines....

when you have a package on BIDS on your machine and you reference a file like c:\somfile everything works ok...

When you...

one case that you cound encounter this error is when one server uses 64bit edition of sql server and the other x86....

Why dont you use excel???

see this

http://msdn.microsoft.com/en-us/library/cc917711.aspx

http://msdn.microsoft.com/en-us/library/cc966418.aspx

Ms White paper that will get you started

delete from arch_table where case_month = @casE_month (non clustered index on Case_month)

That was the problematic statement... I cant see how sql can generate 2 execution plans that have such huge...

The rebuild would have updated stats, hence fixing the problem. An update stats would have worked too.

Option keepplan also fixed the problem...

Select * from sys.dm_db_index_physical_stats

will show you if the index is fragmented Not the Data Pages (with the exception of course of a clustered index), isn't that right ???

Index rebuild...

When sql server starts to execute the code it validates the script...

Validated NOT executes

so the steps are

1. validate exec statement -> ok, continue (DO NOT EXECUTE)

2. Validate insert statement ->...

You cannot add a column and insert a value on the same stored procedure...

When sql server starts to execute the code it validates the script... In your case he sees...

Grant Fritchey (5/10/2010)

---

kastros.george (5/10/2010)

---

use

option keepplan

or somthing like that

i think the problem is that sql server tries to generate an execution plan, aby trying to estimate row size and...

use

option keepplan

or somthing like that

i think the problem is that sql server tries to generate an execution plan, aby trying to estimate row size and row count

Use perfmon...