Showing posts with label page. Show all posts
Showing posts with label page. Show all posts

Friday, March 30, 2012

Launching Web Page From SQL

Hello All,

I'm not very knowledgable about SQL server so I'm not quite sure if this is possible. I want a scheduled task to be ran everyday. (Querying the Database and such). If a certain parameter is met I want a webpage, w/ code behind that will send an email, to be launched.

Is there any way to launch a web page from SQL??

Thanks in advance,

Kyle Landis

Do you want web page to send e-mail only? The SQL Server cansend e-mail too.

Monday, March 19, 2012

Last Page of Group

Hello, i am new to this, but here it goes (only using Crystal about a week)

I am using Crystal XI,I have a financial report, grouped twice.
First by 'main account' then sub-account'.

The detail section contain transaction data. For every new main account a new page is started. My issue is is that occasionally the transactions will need more than one page, upto around 3 or 4, depending on the size of the account, and the number of sub-accounts (the sub account header takes up a lot of space)

I require specific information to be displayed on the last page of group one('end of coalation mark' for our OCR system), and i can't figure out how to determine what is the last page of a group by any means

can anyone help with this?Use formula and write this

if NextIsNull(filed) then
--last page

Last line of page printing at top of next page

Anyone else have this problem and know the solution.
--
Thanks,
Danny BaderWhen I put summary info into a page footer, I got the same problem like you.
Now I'm using table footer to show summary info.
"Danny Bader" wrote:
> Anyone else have this problem and know the solution.
> --
> Thanks,
> Danny Bader

Wednesday, March 7, 2012

Large Textboxes and paging in PDF files

I've got a textbox bound to a text sql server field that contains about four
paragraphs of information. When I export to pdf the page breaks don't work
correctly. It starts a new page unless the entire contents of the field will
fit on the existing page. I would like it to fit what it can on the existing
page and then flow over to the next page as one would expect.
Another thing I noticed is that if I shrink the textbox to about 3.5 inches
then it works as I would like except that it's in a narrow column. Anything
wider than that and the page break issue pops up again. Thanks.I am currently struggling with exactly the same issue. The reason that
making the textbox narrower seems to fix the page break issue is, I believe,
because the resultant narrow column of text is longer than one page can
accommodate, therefore RS knows it has to break the field anyway and so it
just renders it without throwing a new page first. If the textbox can fit
completely on one page then RS bumps it over to the next page. This would be
fine as long as you can turn it off from a property but it doesn't seem like
you can.
Has anyone out there got a way of fixing this or working around it?
Cs.
"MR" wrote:
> I've got a textbox bound to a text sql server field that contains about four
> paragraphs of information. When I export to pdf the page breaks don't work
> correctly. It starts a new page unless the entire contents of the field will
> fit on the existing page. I would like it to fit what it can on the existing
> page and then flow over to the next page as one would expect.
> Another thing I noticed is that if I shrink the textbox to about 3.5 inches
> then it works as I would like except that it's in a narrow column. Anything
> wider than that and the page break issue pops up again. Thanks.

Friday, February 24, 2012

Large report.

My SQL script behind a report produces, say, 10,000 records or more. I
need to show,
at first, only 1st page and - this is important - to pull data from
server only for this 1st page.
In order to avoid performance bottleneck I need to avoid pulling all
data from server! When user clicks next page on client, the client
should extract data from server.
Is there a standard solution for this in SQL Sertver 2000 Reporting
Services?
It looks like a common situation, but I did not find a positive answer
and HOWTO in this group.
StanYou do not have control over this. There is a good reason why. How is
reporting services supposed to apply groups without the data?
I suggest you look at the concept of drill through using jump to report (or
jump to URL).
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rptsrvr9/html/e746e8e2-8af9-4597-8476-18562a92015e.htm
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<smalevanny@.hotmail.com> wrote in message
news:1142338498.985075.219970@.u72g2000cwu.googlegroups.com...
> My SQL script behind a report produces, say, 10,000 records or more. I
> need to show,
> at first, only 1st page and - this is important - to pull data from
> server only for this 1st page.
> In order to avoid performance bottleneck I need to avoid pulling all
> data from server! When user clicks next page on client, the client
> should extract data from server.
> Is there a standard solution for this in SQL Sertver 2000 Reporting
> Services?
> It looks like a common situation, but I did not find a positive answer
> and HOWTO in this group.
> Stan
>

Large report to fit onto 1 page

Hi,

I've browsed the forums and found other posts outlining the same issue and the answer was no..there is no scale to fit option in reporting services.. now a year later i was wondering if anything had been done about this?

Is there anyway to get a 20 column report to fit onto 1 page on printing?

Many thanks

Dave

Have you submitted this suggestion to https://connect.microsoft.com/SQLServer/Feedback ?

If so, let me know the URL and I will also vote on it.

There is nothing in SSRS now that allows "fit to page", but there really should be, especially for the matrix control.

BobP

large query

I have query from SQL server 2000 which returns from database very large.
However I show client only 20 records per page. I need to find way which
allows to get from database only what I need (like top 100). Response from
database about 10mins which is not acceptable.
Look at this article for ideas about paging.
Paging Queries
www.aspfaq.com/2120
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Aleks Kleyn" <AleksKleyn@.OptOnline.net> wrote in message
news:DD4DE5D1-82EF-4E2A-A46A-7E8FB7407135@.microsoft.com...
>I have query from SQL server 2000 which returns from database very large.
>However I show client only 20 records per page. I need to find way which
>allows to get from database only what I need (like top 100). Response from
>database about 10mins which is not acceptable.

Large Page Extensions

Hello
After a reboot on my SQL Server 2000 64 bits the following message appeared
on the Errorlog:
Cannot use Large Page Extensions: Failed to allocate 32MB
I searched Google and the Books On-Line but found nothing about it.
Could someone point to me some documentation about that message? Or explain
what does it means?
Thanks
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.org
On 64-bit platforms, SQL Server makes use of the 'large page' API support
provided by the operating system. You can read more about it here
http://msdn.microsoft.com/library/de...e_support.asp.
The error you're receiving is hinted at in the article, but is due to the
fact that SQL Server cannot get a contiguous region of 32 MB for the large
page region.
Hope that helps.
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Carlos Selonke" <CarlosSelonke@.discussions.microsoft.com> wrote in message
news:73B198C4-7B9B-4063-8866-97D4108B3F06@.microsoft.com...
> Hello
> After a reboot on my SQL Server 2000 64 bits the following message
> appeared
> on the Errorlog:
> Cannot use Large Page Extensions: Failed to allocate 32MB
> I searched Google and the Books On-Line but found nothing about it.
> Could someone point to me some documentation about that message? Or
> explain
> what does it means?
> Thanks
> --
> Carlos Eduardo Selonke de Souza
> http://carlos.geekbunker.org

Large Page Extensions

Hello
After a reboot on my SQL Server 2000 64 bits the following message appeared
on the Errorlog:
Cannot use Large Page Extensions: Failed to allocate 32MB
I searched Google and the Books On-Line but found nothing about it.
Could someone point to me some documentation about that message? Or explain
what does it means?
Thanks
--
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.orgOn 64-bit platforms, SQL Server makes use of the 'large page' API support
provided by the operating system. You can read more about it here
http://msdn.microsoft.com/library/d...ge_support.asp.
The error you're receiving is hinted at in the article, but is due to the
fact that SQL Server cannot get a contiguous region of 32 MB for the large
page region.
Hope that helps.
--
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Carlos Selonke" <CarlosSelonke@.discussions.microsoft.com> wrote in message
news:73B198C4-7B9B-4063-8866-97D4108B3F06@.microsoft.com...
> Hello
> After a reboot on my SQL Server 2000 64 bits the following message
> appeared
> on the Errorlog:
> Cannot use Large Page Extensions: Failed to allocate 32MB
> I searched Google and the Books On-Line but found nothing about it.
> Could someone point to me some documentation about that message? Or
> explain
> what does it means?
> Thanks
> --
> Carlos Eduardo Selonke de Souza
> http://carlos.geekbunker.org

Large Page Extensions

Hello
After a reboot on my SQL Server 2000 64 bits the following message appeared
on the Errorlog:
Cannot use Large Page Extensions: Failed to allocate 32MB
I searched Google and the Books On-Line but found nothing about it.
Could someone point to me some documentation about that message? Or explain
what does it means?
Thanks
--
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.orgOn 64-bit platforms, SQL Server makes use of the 'large page' API support
provided by the operating system. You can read more about it here
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/memory/base/large_page_support.asp.
The error you're receiving is hinted at in the article, but is due to the
fact that SQL Server cannot get a contiguous region of 32 MB for the large
page region.
Hope that helps.
--
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Carlos Selonke" <CarlosSelonke@.discussions.microsoft.com> wrote in message
news:73B198C4-7B9B-4063-8866-97D4108B3F06@.microsoft.com...
> Hello
> After a reboot on my SQL Server 2000 64 bits the following message
> appeared
> on the Errorlog:
> Cannot use Large Page Extensions: Failed to allocate 32MB
> I searched Google and the Books On-Line but found nothing about it.
> Could someone point to me some documentation about that message? Or
> explain
> what does it means?
> Thanks
> --
> Carlos Eduardo Selonke de Souza
> http://carlos.geekbunker.org

Large number of records and Small page size?

Hi there. I'm a beginner of reporting service, and so I'm not sure if
this question belongs to the FAQ.
Suppose a report has a query which can potentially retrieves large
number of records, say, 500,000 records. The report has a only a page
size of 50 records (i.e. 50 records to be displayed at a time). When a
user view this report in the reporting service at the IIS, does the
report service pull all 500,000 records from the database server to the
IIS, or does it only pull 50 record from database server to IIS at a
time?
Thanks
DomI forgot to mention that I'm using SQL Server 2000 as the data-source,
and Reporting Service 2000 (the one published in 2004).
Thanks
Dom
dom...@.hotmail.com wrote:
> Hi there. I'm a beginner of reporting service, and so I'm not sure if
> this question belongs to the FAQ.
> Suppose a report has a query which can potentially retrieves large
> number of records, say, 500,000 records. The report has a only a page
> size of 50 records (i.e. 50 records to be displayed at a time). When a
> user view this report in the reporting service at the IIS, does the
> report service pull all 500,000 records from the database server to the
> IIS, or does it only pull 50 record from database server to IIS at a
> time?
> Thanks
> Dom|||Hi,
The reporting service run the query and pull all the data once. it does not
pull 50 record each time you click next. once it get the record it pulls from
the memory and show to you. The custom paging of pulling the record from
database each time when you click next is not done by report manager or
reporing service.
Thanks
Bava
"domtam@.hotmail.com" wrote:
> I forgot to mention that I'm using SQL Server 2000 as the data-source,
> and Reporting Service 2000 (the one published in 2004).
> Thanks
> Dom
> dom...@.hotmail.com wrote:
> > Hi there. I'm a beginner of reporting service, and so I'm not sure if
> > this question belongs to the FAQ.
> >
> > Suppose a report has a query which can potentially retrieves large
> > number of records, say, 500,000 records. The report has a only a page
> > size of 50 records (i.e. 50 records to be displayed at a time). When a
> > user view this report in the reporting service at the IIS, does the
> > report service pull all 500,000 records from the database server to the
> > IIS, or does it only pull 50 record from database server to IIS at a
> > time?
> >
> > Thanks
> > Dom
>|||Thanks for your reply.
If the query can potentially return large number of records (say,
500,000) records, all these records will be put to the memory of the
IIS server hosting the report even though each page may show ony 50
records. Is this what you mean?
In this case, this can impose lots of stress on the memory of the IIS
server, especially there are multiple users viewing reports of large
size. How should we handle large report (of small page size) in this
situation? I believe this is a common scenario in Reporting Service
community, right?
If it is the ASP.NET datagrid (instead of report) that displays these
records, we can use custom paging to handle this kinda large result-set
query situation. In other words, we will pull 50 records at a time. Is
there any similar technique for Reporting Service?
Thanks
Dominic
Bava Mani wrote:
> Hi,
> The reporting service run the query and pull all the data once. it does not
> pull 50 record each time you click next. once it get the record it pulls from
> the memory and show to you. The custom paging of pulling the record from
> database each time when you click next is not done by report manager or
> reporing service.
> Thanks
> Bava
> "domtam@.hotmail.com" wrote:
> > I forgot to mention that I'm using SQL Server 2000 as the data-source,
> > and Reporting Service 2000 (the one published in 2004).
> >
> > Thanks
> > Dom
> > dom...@.hotmail.com wrote:
> > > Hi there. I'm a beginner of reporting service, and so I'm not sure if
> > > this question belongs to the FAQ.
> > >
> > > Suppose a report has a query which can potentially retrieves large
> > > number of records, say, 500,000 records. The report has a only a page
> > > size of 50 records (i.e. 50 records to be displayed at a time). When a
> > > user view this report in the reporting service at the IIS, does the
> > > report service pull all 500,000 records from the database server to the
> > > IIS, or does it only pull 50 record from database server to IIS at a
> > > time?
> > >
> > > Thanks
> > > Dom
> >
> >