If it runs fine for other parameters but not for this one, it might be a bad parameter sniffing issue.  The stored proc is third party so you can't modify...

I would start by checking indexes.  Replication usually doesn't copy indexes, so the replicated DB most likely doesn't have indexes that Prod does.

Another thing to check is permissions in SSRS need to be given all the way up the folder chain.  If you have a Reports folder and within that you give...

AFAIK you have to use the full address http://servername/reports because, well,  that's the address.  I save the keystrokes of typing the report manager addresses on our various servers...

Try adding to your query something like:

WHERE (col1 IN (@parm) or @parm IS NULL)

Then in Visual Studio make sure the parameter @parm can be NULL.

It looks like you probably want to group your report on AccountNumber and/or PatientName.  That gives you a header with that grouping and sub-listings with the details.

A couple suggestions - one, you could try putting the row count text box in the footer, so it will always be at the bottom.  Or, perhaps placing the data...

Make sure the top border of the textbox below has the same settings that you want for your bottom border.  I've seen instances where the border settings for a neighboring...

Do you have clustering/load balancing in your environment?  We had an issue with report subscriptions sometimes failing, and it turned out that we had two servers in the cluster that...

Part of the problem may be there is an errant comma in your Partition:

PARTITION BY [c.col2,]

Should be (if you only want to partition on the one field):

I have used SSRS 2008 against a SQL 2005 DB, so I know backward compatibility was part of the package then. I would assume it still is.

I'm not sure about plan guides, but in regular queries it's legal in 2005. If you are using aliases the nolock needs to come after the alias.

This will generate...

My understanding is you can change data on the replicated server, but it will remain changed until the subscriptions are re-initialized (which you could do nightly).  However, I think altering...

Pasting the error into google yields this as the first hit: https://support.microsoft.com/en-us/help/106167/error-message-not-enough-server-storage-is-available-to-process-this-c
It seems to be a Windows error, not SQL.

I have mainly used shared datasets where I have common lookups for parameters in reports (location, section, accounting category, etc.).  Rather than make a new dataset every time I have...