"Troy" <Troy@discussions.microsoft.com> wrote in message
news:1DD492E2-DD58-4AA1-A648-F14BB71C796B@microsoft.com...
> Thanks Bruce - well that is what I figured also, but I can't believe that
> returning even a small subset of data would blow out all my RAM and start
> swapping out.
> I have 512MB - which I know is pretty marginal in terms of a dev machine,
> however in terms of dev with VS, reporting is all it is used for.
> I take it then that there is no other setting which might cause this - ie
> if
> it is pulling all the results of the table to the local machine and then
> querying it - or something dumb like that?
>
> "Bruce L-C [MVP]" wrote:
>
>> How much memory does your development machine have. Seems to me like you
>> have run out of RAM and you are thrashing (swapping out to disk). I
>> develop
>> in 2005 and so far have never seen this. I have a gig on my development
>> machine.
>>
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Troy" <Troy@discussions.microsoft.com> wrote in message
>> news:E46C5544-AAC5-40CF-8F49-E63E001BDBBF@microsoft.com...
>> > Hi,
>> >
>> > Hopefully someone with a bit of experience with Visual Studio 2005 and
>> > RS
>> > can offer some advice.
>> > I am using VS2005, sourcing a SQL2K database (but deploying to a SQL2k5
>> > RS),
>> > and am simply trying to do a select of about 800 records from one table
>> > (ie
>> > no joins).
>> >
>> > The report has only one grouping field - and in essence is overly
>> > simplistic
>> > just to try and understand where my issue is.
>> >
>> > When trying to preview the report, it seems to take for ever - the hard
>> > disk
>> > starts flogging away, and processor usage increases - to the point
>> > where i
>> > eventually stop the rendering of the report (have waited in excess of
>> > 15
>> > minutes!!!).
>> >
>> > I have managed to get results back if I restrict the results of the
>> > query
>> > to
>> > one line - or even to 200 lines (however this takes about 5min).
>> >
>> > Each time the hard disk goes nuts and processor usage increases.
>> >
>> > Any ideas what is happening here? Is it a configuration setting that I
>> > am
>> > overlooking, or something more sinister?
>> >
>> > The report runs fine once it is deployed to the RS - so it is just
>> > something
>> > with VS2005 - but what?
>> >
>> > Thanks in advance for any assistance on this.
>> >
>> > Troy
>> >
>>
>>
>>

"Troy" <Troy@discussions.microsoft.com> wrote in message
news:4F837EB3-B49D-4D1C-8580-DF2E4B5DF045@microsoft.com...
> Hi Bruce,
>
> Just installed another 512 - so was sitting at 1gig total, and same
> scenario....
>
> Went into RS while waiting for the preview to render and raised the same
> report - result back in 3 seconds.....
>
> I am well lost now.....
>
> Any thoughts?
>
> Cheers
> Troy
>
> "Bruce L-C [MVP]" wrote:
>
>> The preview tab is using the same code as the render for the server.
>> Visual
>> Studio itself is pretty big. I bet if you even put in another 256 it
>> would
>> make a big difference.
>>
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Troy" <Troy@discussions.microsoft.com> wrote in message
>> news:1DD492E2-DD58-4AA1-A648-F14BB71C796B@microsoft.com...
>> > Thanks Bruce - well that is what I figured also, but I can't believe
>> > that
>> > returning even a small subset of data would blow out all my RAM and
>> > start
>> > swapping out.
>> > I have 512MB - which I know is pretty marginal in terms of a dev
>> > machine,
>> > however in terms of dev with VS, reporting is all it is used for.
>> > I take it then that there is no other setting which might cause this -
>> > ie
>> > if
>> > it is pulling all the results of the table to the local machine and
>> > then
>> > querying it - or something dumb like that?
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> How much memory does your development machine have. Seems to me like
>> >> you
>> >> have run out of RAM and you are thrashing (swapping out to disk). I
>> >> develop
>> >> in 2005 and so far have never seen this. I have a gig on my
>> >> development
>> >> machine.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Troy" <Troy@discussions.microsoft.com> wrote in message
>> >> news:E46C5544-AAC5-40CF-8F49-E63E001BDBBF@microsoft.com...
>> >> > Hi,
>> >> >
>> >> > Hopefully someone with a bit of experience with Visual Studio 2005
>> >> > and
>> >> > RS
>> >> > can offer some advice.
>> >> > I am using VS2005, sourcing a SQL2K database (but deploying to a
>> >> > SQL2k5
>> >> > RS),
>> >> > and am simply trying to do a select of about 800 records from one
>> >> > table
>> >> > (ie
>> >> > no joins).
>> >> >
>> >> > The report has only one grouping field - and in essence is overly
>> >> > simplistic
>> >> > just to try and understand where my issue is.
>> >> >
>> >> > When trying to preview the report, it seems to take for ever - the
>> >> > hard
>> >> > disk
>> >> > starts flogging away, and processor usage increases - to the point
>> >> > where i
>> >> > eventually stop the rendering of the report (have waited in excess
>> >> > of
>> >> > 15
>> >> > minutes!!!).
>> >> >
>> >> > I have managed to get results back if I restrict the results of the
>> >> > query
>> >> > to
>> >> > one line - or even to 200 lines (however this takes about 5min).
>> >> >
>> >> > Each time the hard disk goes nuts and processor usage increases.
>> >> >
>> >> > Any ideas what is happening here? Is it a configuration setting that
>> >> > I
>> >> > am
>> >> > overlooking, or something more sinister?
>> >> >
>> >> > The report runs fine once it is deployed to the RS - so it is just
>> >> > something
>> >> > with VS2005 - but what?
>> >> >
>> >> > Thanks in advance for any assistance on this.
>> >> >
>> >> > Troy
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>

"Troy" <Troy@discussions.microsoft.com> wrote in message
news:9267E59E-F019-45E4-BB71-8F9BB01056CB@microsoft.com...
> Might try a reinstall and see whether shuffles anything around
> Thanks for the thoughts though!
> If anyone else has any other ideas - please let me know
>
> "Bruce L-C [MVP]" wrote:
>
>> Isn't that just like reality to get in the way of a good theory. Very
>> weird.
>> Sorry. I am out of ideas. This is very weird.
>>
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Troy" <Troy@discussions.microsoft.com> wrote in message
>> news:4F837EB3-B49D-4D1C-8580-DF2E4B5DF045@microsoft.com...
>> > Hi Bruce,
>> >
>> > Just installed another 512 - so was sitting at 1gig total, and same
>> > scenario....
>> >
>> > Went into RS while waiting for the preview to render and raised the
>> > same
>> > report - result back in 3 seconds.....
>> >
>> > I am well lost now.....
>> >
>> > Any thoughts?
>> >
>> > Cheers
>> > Troy
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> The preview tab is using the same code as the render for the server.
>> >> Visual
>> >> Studio itself is pretty big. I bet if you even put in another 256 it
>> >> would
>> >> make a big difference.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Troy" <Troy@discussions.microsoft.com> wrote in message
>> >> news:1DD492E2-DD58-4AA1-A648-F14BB71C796B@microsoft.com...
>> >> > Thanks Bruce - well that is what I figured also, but I can't believe
>> >> > that
>> >> > returning even a small subset of data would blow out all my RAM and
>> >> > start
>> >> > swapping out.
>> >> > I have 512MB - which I know is pretty marginal in terms of a dev
>> >> > machine,
>> >> > however in terms of dev with VS, reporting is all it is used for.
>> >> > I take it then that there is no other setting which might cause
>> >> > this -
>> >> > ie
>> >> > if
>> >> > it is pulling all the results of the table to the local machine and
>> >> > then
>> >> > querying it - or something dumb like that?
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> How much memory does your development machine have. Seems to me
>> >> >> like
>> >> >> you
>> >> >> have run out of RAM and you are thrashing (swapping out to disk). I
>> >> >> develop
>> >> >> in 2005 and so far have never seen this. I have a gig on my
>> >> >> development
>> >> >> machine.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Troy" <Troy@discussions.microsoft.com> wrote in message
>> >> >> news:E46C5544-AAC5-40CF-8F49-E63E001BDBBF@microsoft.com...
>> >> >> > Hi,
>> >> >> >
>> >> >> > Hopefully someone with a bit of experience with Visual Studio
>> >> >> > 2005
>> >> >> > and
>> >> >> > RS
>> >> >> > can offer some advice.
>> >> >> > I am using VS2005, sourcing a SQL2K database (but deploying to a
>> >> >> > SQL2k5
>> >> >> > RS),
>> >> >> > and am simply trying to do a select of about 800 records from one
>> >> >> > table
>> >> >> > (ie
>> >> >> > no joins).
>> >> >> >
>> >> >> > The report has only one grouping field - and in essence is overly
>> >> >> > simplistic
>> >> >> > just to try and understand where my issue is.
>> >> >> >
>> >> >> > When trying to preview the report, it seems to take for ever -
>> >> >> > the
>> >> >> > hard
>> >> >> > disk
>> >> >> > starts flogging away, and processor usage increases - to the
>> >> >> > point
>> >> >> > where i
>> >> >> > eventually stop the rendering of the report (have waited in
>> >> >> > excess
>> >> >> > of
>> >> >> > 15
>> >> >> > minutes!!!).
>> >> >> >
>> >> >> > I have managed to get results back if I restrict the results of
>> >> >> > the
>> >> >> > query
>> >> >> > to
>> >> >> > one line - or even to 200 lines (however this takes about 5min).
>> >> >> >
>> >> >> > Each time the hard disk goes nuts and processor usage increases.
>> >> >> >
>> >> >> > Any ideas what is happening here? Is it a configuration setting
>> >> >> > that
>> >> >> > I
>> >> >> > am
>> >> >> > overlooking, or something more sinister?
>> >> >> >
>> >> >> > The report runs fine once it is deployed to the RS - so it is
>> >> >> > just
>> >> >> > something
>> >> >> > with VS2005 - but what?
>> >> >> >
>> >> >> > Thanks in advance for any assistance on this.
>> >> >> >
>> >> >> > Troy
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>