Bug in Report Designer - can anyone reproduce?

I think I've discovered a serious bug with the Report Designer, which
causes devenv.exe to take up 100% CPU and skyrocket in memory usage.
Here's how I got to it:
-Create a report with three parameters: The first two are dates (start
date and end date for a date range) and the third is a String
(employee name).
-Create a query to auto-populate both date fields.
-Create a query to fill the String parameter with values that are
dependant on the first two date parameters (return employees that were
active during the range of the two parameters, for instance).
This works okay when deployed, but in Preview Mode in Visual Studio,
after changing either of the Date parameters from their default value,
VS seems to get stuck in an infinite loop when attempting to
re-populate the third parameter with employee names.
Can anyone reproduce this?
Thanks,
Matthew Brown
Viecore IncYes, I have seen this (and like you saw that it was not a problem with
deployed reports). Once I saw that deployed was OK then I would deploy for
testing (a bit of a pain but I did not have many reports with this issue).
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Matthew Brown" <octavius@.gmail.com> wrote in message
news:lgao41htssrgtq5kqv56d2sernj9fka3eu@.4ax.com...
> I think I've discovered a serious bug with the Report Designer, which
> causes devenv.exe to take up 100% CPU and skyrocket in memory usage.
> Here's how I got to it:
> -Create a report with three parameters: The first two are dates (start
> date and end date for a date range) and the third is a String
> (employee name).
> -Create a query to auto-populate both date fields.
> -Create a query to fill the String parameter with values that are
> dependant on the first two date parameters (return employees that were
> active during the range of the two parameters, for instance).
> This works okay when deployed, but in Preview Mode in Visual Studio,
> after changing either of the Date parameters from their default value,
> VS seems to get stuck in an infinite loop when attempting to
> re-populate the third parameter with employee names.
> Can anyone reproduce this?
> Thanks,
> Matthew Brown
> Viecore Inc
>|||Since I am using calls to a custom assembly to retrieve strings in my
reports, Report Designer Hangs visual studio with this behavior with ALL my
reports. I have to kill it with the task manager. I think this is a very
serious issue.
I would think anyone localizing strings within a report with RS 2000 would
have the same issue as I do. It makes the preview functionality of Report
Designer useless. I would love to have a fix for this in RS 2000.
Thanks for any help or indication of priority, good or bad,
Andrew
"Bruce L-C [MVP]" wrote:
> Yes, I have seen this (and like you saw that it was not a problem with
> deployed reports). Once I saw that deployed was OK then I would deploy for
> testing (a bit of a pain but I did not have many reports with this issue).
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Matthew Brown" <octavius@.gmail.com> wrote in message
> news:lgao41htssrgtq5kqv56d2sernj9fka3eu@.4ax.com...
> > I think I've discovered a serious bug with the Report Designer, which
> > causes devenv.exe to take up 100% CPU and skyrocket in memory usage.
> > Here's how I got to it:
> >
> > -Create a report with three parameters: The first two are dates (start
> > date and end date for a date range) and the third is a String
> > (employee name).
> > -Create a query to auto-populate both date fields.
> > -Create a query to fill the String parameter with values that are
> > dependant on the first two date parameters (return employees that were
> > active during the range of the two parameters, for instance).
> >
> > This works okay when deployed, but in Preview Mode in Visual Studio,
> > after changing either of the Date parameters from their default value,
> > VS seems to get stuck in an infinite loop when attempting to
> > re-populate the third parameter with employee names.
> >
> > Can anyone reproduce this?
> >
> > Thanks,
> > Matthew Brown
> > Viecore Inc
> >
> >
>
>|||Hmmm, the symptom might be the same (hangs Report Designer) but your
description does not seem to have anything to do with what we were talking
about. I have not seen your symptom before (either personally or via a post
in the newsgroup). I use a small amount of custom code but mine is code
behind reports, not a custom assembly. I do know there are definitely
specific steps to be taken when using custom assemblies. I suggest posting
with a subject of "Custom assembly hangs Report Designer) and see if someone
who has used custom assemblies has any ideas.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"skillet" <skillet@.discussions.microsoft.com> wrote in message
news:B2ABA9D3-2934-43BE-AA18-41880E3B6480@.microsoft.com...
> Since I am using calls to a custom assembly to retrieve strings in my
> reports, Report Designer Hangs visual studio with this behavior with ALL
my
> reports. I have to kill it with the task manager. I think this is a very
> serious issue.
> I would think anyone localizing strings within a report with RS 2000 would
> have the same issue as I do. It makes the preview functionality of Report
> Designer useless. I would love to have a fix for this in RS 2000.
> Thanks for any help or indication of priority, good or bad,
> Andrew
> "Bruce L-C [MVP]" wrote:
> > Yes, I have seen this (and like you saw that it was not a problem with
> > deployed reports). Once I saw that deployed was OK then I would deploy
for
> > testing (a bit of a pain but I did not have many reports with this
issue).
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Matthew Brown" <octavius@.gmail.com> wrote in message
> > news:lgao41htssrgtq5kqv56d2sernj9fka3eu@.4ax.com...
> > > I think I've discovered a serious bug with the Report Designer, which
> > > causes devenv.exe to take up 100% CPU and skyrocket in memory usage.
> > > Here's how I got to it:
> > >
> > > -Create a report with three parameters: The first two are dates (start
> > > date and end date for a date range) and the third is a String
> > > (employee name).
> > > -Create a query to auto-populate both date fields.
> > > -Create a query to fill the String parameter with values that are
> > > dependant on the first two date parameters (return employees that were
> > > active during the range of the two parameters, for instance).
> > >
> > > This works okay when deployed, but in Preview Mode in Visual Studio,
> > > after changing either of the Date parameters from their default value,
> > > VS seems to get stuck in an infinite loop when attempting to
> > > re-populate the third parameter with employee names.
> > >
> > > Can anyone reproduce this?
> > >
> > > Thanks,
> > > Matthew Brown
> > > Viecore Inc
> > >
> > >
> >
> >
> >|||That is possible. My situation is fairly simple; I just call a custom code
function which calls right out to a custom assembly, which in turn returns a
string. once I have a few of these in the report the designer no longer
functions, flickering as it tries to refresh (apparently). There are
certainly steps to be taken with respect to referencing and securing a custom
assembly, but I don't think a configuration problem with the custom assembly
would cause this behavior in the Report Designer.
Instead, it seems that the Designer is trying to refresh its fields very
often, and when several fields call out to a custom assembly, the designer's
desired refresh cycle is faster than all of the calls can be completed (?).
Thanks for your help.
"Bruce L-C [MVP]" wrote:
> Hmmm, the symptom might be the same (hangs Report Designer) but your
> description does not seem to have anything to do with what we were talking
> about. I have not seen your symptom before (either personally or via a post
> in the newsgroup). I use a small amount of custom code but mine is code
> behind reports, not a custom assembly. I do know there are definitely
> specific steps to be taken when using custom assemblies. I suggest posting
> with a subject of "Custom assembly hangs Report Designer) and see if someone
> who has used custom assemblies has any ideas.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>

Bound Control on Access Form Causing High Memory Usage on SQL Server

I got about 50 Access users every day using the SQL Server
2000 database. At the end of the day, SQL Server always
ran out of the memory. Someone told me this is because of
the bound connection on the Access form causing the memory
leak. Is there a way to fix this problem without changing
my Access form design.not really.
acccess bound controls open numerous connections PER FORM.
this is not good.
only way to fix it would be to code your connectivity manually.
GAJ|||I currently have 2 GB physical memory which could last for
about 2 to 3 days if no one runs a big report. What if I
increase the memory size to 4 GB?

>--Original Message--
>not really.
>acccess bound controls open numerous connections PER FORM.
>this is not good.
>only way to fix it would be to code your connectivity
manually.
>
>GAJ
>
>.
>|||I suspect you will still eventually run out of connections and\or memory.
instead of using bound controls, write the code manually to populate
controls. that way you have explicit control over connection management.
will this work for you ?
GAJ|||Ken,
Are you sure it is really a memory leak? SQL Server will not release memory
once it grabs it unless the OS specifically calls for it. That is by
design. http://www.support.microsoft.com/?id=321363 Do you have things
other than sql server running on the same machine? If so you may want to
set your max memory setting to something less than the default of max and
see if that helps.
Andrew J. Kelly
SQL Server MVP
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:bf6601c3ecfa$9f12e2a0$a401280a@.phx.gbl...
> I got about 50 Access users every day using the SQL Server
> 2000 database. At the end of the day, SQL Server always
> ran out of the memory. Someone told me this is because of
> the bound connection on the Access form causing the memory
> leak. Is there a way to fix this problem without changing
> my Access form design.

Bound Control on Access Form Causing High Memory Usage on SQL Server

I got about 50 Access users every day using the SQL Server
2000 database. At the end of the day, SQL Server always
ran out of the memory. Someone told me this is because of
the bound connection on the Access form causing the memory
leak. Is there a way to fix this problem without changing
my Access form design.not really.
acccess bound controls open numerous connections PER FORM.
this is not good.
only way to fix it would be to code your connectivity manually.
GAJ|||I currently have 2 GB physical memory which could last for
about 2 to 3 days if no one runs a big report. What if I
increase the memory size to 4 GB?
>--Original Message--
>not really.
>acccess bound controls open numerous connections PER FORM.
>this is not good.
>only way to fix it would be to code your connectivity
manually.
>
>GAJ
>
>.
>|||I suspect you will still eventually run out of connections and\or memory.
instead of using bound controls, write the code manually to populate
controls. that way you have explicit control over connection management.
will this work for you ?
GAJ|||Ken,
Are you sure it is really a memory leak? SQL Server will not release memory
once it grabs it unless the OS specifically calls for it. That is by
design. http://www.support.microsoft.com/?id=321363 Do you have things
other than sql server running on the same machine? If so you may want to
set your max memory setting to something less than the default of max and
see if that helps.
--
Andrew J. Kelly
SQL Server MVP
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:bf6601c3ecfa$9f12e2a0$a401280a@.phx.gbl...
> I got about 50 Access users every day using the SQL Server
> 2000 database. At the end of the day, SQL Server always
> ran out of the memory. Someone told me this is because of
> the bound connection on the Access form causing the memory
> leak. Is there a way to fix this problem without changing
> my Access form design.