Showing posts with label nvarchar. Show all posts
Showing posts with label nvarchar. Show all posts

Friday, March 9, 2012

large value data type (nvarchar(max))

hi,

I have inserted a new column in my db table (type: nvarchar(max))
now I can't process the cube anymore ... is there a possibility to store large text files in the cube?

thanks,

rhapsy

Hi Rhapsy

What are you trying to achieve with this data? Would it not be easier to try and have an action to get that text if it is needed?

Regards

Mike

|||hey mike,

probably it would be easier, but I'd like to get all my information from the same source ...
and I'm a little bit curious if thias is possible ...

thanks,
rhapsy

Monday, February 20, 2012

Large fields freeze the report generation

Hi Group,
I have this subreport that displays information from 2 fields of type
nvarchar(4000).
If I try to preview the subreport from the designer, everything works fine -
there are about 2 pages of information displayed. Export to pdf works
normally.
After deploying it on the server, if I use the
http://server_name/Reports/... again everything works fine. Exporting to pdf
produces a 2-3 pages file in about 10 seconds.
The report that contains this subreport works fine - export to pdf goes
through with no problems.
But if I try to use our application that generates / displays the reports,
it just hangs there, after calling the Render method.
The aspnet_wp process on the server stays at about 93% until the Render
method times out (approx. 10 minutes).
I tried removing the two large nvarchar fields from the subreport - the
report starts working fine like any other report.
The information that should be displayed in the report is not even so much -
as I said before, it should generate about 2-3 pages in pdf.
We have more than 200 reports working fine, none of them complained about
large nvarchar fields.
Did anybody have this type of problem ?
Please help !
Thank you,
Andrei.Correction :
After more tests, this is what I have:
Generating the main report with the Report Manager on the server
(http://server/Reports/...) produces an output in 10 seconds.
But trying to export as PDF will lock the process until timeout.
If I remove the fields of type nvarchar(4000) from the SUBreport, then the
report export to PDF works fine.
Generating the SUBreport with the Report Manager on the server
(http://server/Reports/...) produces an output in less than 10 seconds
The export to PDF works fine.
Thank you,
Andrei.
"Andrei" <andrei.toma@.era-environmental.com> wrote in message
news:esEORK8EHHA.2464@.TK2MSFTNGP06.phx.gbl...
> Hi Group,
> I have this subreport that displays information from 2 fields of type
> nvarchar(4000).
> If I try to preview the subreport from the designer, everything works
> fine - there are about 2 pages of information displayed. Export to pdf
> works normally.
> After deploying it on the server, if I use the
> http://server_name/Reports/... again everything works fine. Exporting to
> pdf produces a 2-3 pages file in about 10 seconds.
> The report that contains this subreport works fine - export to pdf goes
> through with no problems.
> But if I try to use our application that generates / displays the reports,
> it just hangs there, after calling the Render method.
> The aspnet_wp process on the server stays at about 93% until the Render
> method times out (approx. 10 minutes).
> I tried removing the two large nvarchar fields from the subreport - the
> report starts working fine like any other report.
> The information that should be displayed in the report is not even so
> much - as I said before, it should generate about 2-3 pages in pdf.
> We have more than 200 reports working fine, none of them complained about
> large nvarchar fields.
> Did anybody have this type of problem ?
> Please help !
> Thank you,
> Andrei.
>