problems with temporary tables in reports

Question

problems with temporary tables in reports

Viewing 8 posts - 16 through 22 (of 22 total)

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

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

Then I guess I'm done. I can't see anything wrong with the stored procedure. There are several ways to rewrite it, but those are superficial when you look at the fact you are having a problem calling the stored proc from a report.

kodalisridevi Right there with Babe Points: 752 More actions · Answer 2

kodalisridevi

Right there with Babe

Points: 752

April 18, 2012 at 1:28 pm

#1475658

yes, I am getting the error here..

SQLRNNR SSC Guru Points: 281334 More actions · Answer 3

Are you using the report wizard or did you try to manually create a blank report?

Have you tried altering the dataset to use a command and type execute procname rather than using the stored proc type?

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

kodalisridevi Right there with Babe Points: 752 More actions · Answer 4

Report Wizard:

There is an error in the query. Implicit conversion from data type sql_variant to datetime is not allowed. Use the CONVERT function to run this query.

I am getting the above error message.

Manually :

Invalid Object Name : #Orderstatics.

But, when I am tried with table variables it's working fine( both report Wizard & Manually) .

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

Not enough information to really help.

Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ and follow the instructions on what information to post and how to post it. The more information you provide, the better answers you will get.

Will also need to see the code for your stored procedure. << Done

Need the CREATE TABLE statements for the base tables in the stored procedure.

SQLRNNR SSC Guru Points: 281334 More actions · Answer 6

Then just use a table variable. The only reason to not table variables for this report would be if there is a serious performance impact running the proc.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Conficker SSCommitted Points: 1567 More actions · Answer 7

You gonna Love it....!

Add SET FMTONLY OFF in your proc at top and done.

thanks

Conficker SSCommitted Points: 1567 More actions · Answer 8

Add SET FMTONLY OFF before SELECT statement in your proc and you Done...!:w00t: