Viewing 15 posts - 6,361 through 6,375 (of 19,564 total)
personal computer or work?
local admin?
have you logged in by chance with the wrong account?
Do you have this file on your computer?
"C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\PROFILER.EXE"
April 18, 2012 at 2:31 pm
Stefan Krzywicki (4/18/2012)
jcrawf02 (4/18/2012)
Stefan Krzywicki (4/18/2012)
Scope for variables in SSIS are utter crap, it'd be better if scope didn't even exist here. Yes, I hear it...
April 18, 2012 at 2:12 pm
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.
April 18, 2012 at 1:52 pm
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...
April 18, 2012 at 1:38 pm
Brandie Tarvin (4/18/2012)
We've all heard about the admin assistant who switched from typewriters to computers and...
April 18, 2012 at 1:32 pm
kodalisridevi (4/18/2012)
ADD-->> Report --> NewItem -->> Report -->> Dataset -->>commandtype--'Storedprocedure'-->>Querystring--'Procedurename'
And when you test the dataset here, it errors?
April 18, 2012 at 1:24 pm
I would say that the optimizer deems it too complex and it probably throws a memory error trying to cache it. This sort of thing can happen with vary...
April 18, 2012 at 1:12 pm
SQLKnowItAll (4/18/2012)
Sean Lange (4/18/2012)
As I posted in the other thread. The timestamp datatype is deprecated. http://msdn.microsoft.com/en-us/library/ms182776%28v=sql.105%29.aspxUse datetime to record datetime information.
I think since it is used in MAX(), it...
April 18, 2012 at 1:00 pm
So the question remains, how are you calling the stored procedure in your dataset?
April 18, 2012 at 12:59 pm
Looks like you started a couple new threads for this as well.
Further replies, please post here:
http://www.sqlservercentral.com/Forums/Topic1285914-391-1.aspx
April 18, 2012 at 12:52 pm
Sounds like you are not calling the stored proc then because the temp table in the proc is
#Orderstastics
Either that, or you have an error within the proc that you corrected...
April 18, 2012 at 12:49 pm
charles-1011021 (4/18/2012)
April 18, 2012 at 12:48 pm
How are you calling the stored procedure from SSRS?
One of the things I do differently than you (and since they work on my end), is to list out the columns...
April 18, 2012 at 12:42 pm
Viewing 15 posts - 6,361 through 6,375 (of 19,564 total)