How to show data at the bottom with multiple section?

I have three report footer setion. The first two section has a subreport in it. The last section has the grand total of a amount to both of the subreports.

I want to be able to show all three of these report footer section at the bottom of the page.

I have try the PrintAtBottomOfPage properties. I set it to TRUE to all of the report footer section. When I run the report, each section just shown on it own page.

Is there is a way to have all three section onto one page and on top of each other, not overlaying each other or showing on it own page?HI,
PrintAtBottomOfPage prints on the each pages bottom, so when this works
it still shows inside the Subreports bottm, if u want to get a value from sub report to main report use

1. Have a SHARED Variable(s) in a formula(s) for each of u r subreport(s)
2. Place those above the subreport(s) in the main Rpt, preferabblyy in the main reports header
3. in side the Subreports use a formula to sum u r values using
WhilePrintingRecords function to a varible u have declared 4 that Rpt.
(do this to u r all sub reports), place this formula in u r detail line of records printing (supress it, coz u need only the final answer).
4. in the main report sum the variable of sub reports declared in the main
or show seperatly as u wish in u r footer of main.

Favaz.|||I just want all three of the report footer section to be shown on the bottom of the same report of the first page and the subreport has the ability to GROW if there is a lot of data.

I just want all of the three report footer section to be all in the same page with my DETAILS section and just one page will be printed out.

I will not be pulling any variable from the subreport.|||Ummm .... I'm also having the same problem as his. Does anyone know the answer to his question?

please reply!

How to set up the transaction log file properties?

Hello Guys,
I have question concerning the log file size:
I have a DB that receives a massive amount of data every two days and
several Transaction (USP) and delete records are usually done on it.
During these operations, the log size goes up until 32 Mo.
the size of the .mdf is 9Mo and .ldf is 14Mo
The DB is set to FULL and a backup DB and LOG is performed.
I set up the autoshink as well. is it required?
Why the log file increase so much and how to set up correctly the
transaction log file properties?
Thanks on advance.
Inaina
> I set up the autoshink as well. is it required?
No, disable this option
> Why the log file increase so much and how to set up correctly the
> transaction log file properties?
Why do you concern about that the log file is growing? That means that SQL
Server needs more virtual log files to deal with data. Make sure that you
have a free space enough for log file
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1169025984.073903.91700@.v45g2000cwv.googlegroups.com...
> Hello Guys,
> I have question concerning the log file size:
> I have a DB that receives a massive amount of data every two days and
> several Transaction (USP) and delete records are usually done on it.
> During these operations, the log size goes up until 32 Mo.
> the size of the .mdf is 9Mo and .ldf is 14Mo
> The DB is set to FULL and a backup DB and LOG is performed.
> I set up the autoshink as well. is it required?
> Why the log file increase so much and how to set up correctly the
> transaction log file properties?
>
> Thanks on advance.
> Ina
>|||On 17.01.2007 10:26, ina wrote:
> I have a DB that receives a massive amount of data every two days and
> several Transaction (USP) and delete records are usually done on it.
> During these operations, the log size goes up until 32 Mo.
What unit is that? Megabytes? If so this is really a small DB you
should not worry about sizes in that area at all.
> the size of the .mdf is 9Mo and .ldf is 14Mo
> The DB is set to FULL and a backup DB and LOG is performed.
> I set up the autoshink as well. is it required?
As Uri pointed out, rather switch this off since you only waste
performance. The log will grow and shrink anyway so you can leave it at
the largest size.
> Why the log file increase so much and how to set up correctly the
> transaction log file properties?
Because apparently you DB needs the space (you mention "massive inserts").
Kind regards
robert|||Thanks :)
mdf: 9 MO (Mega Octets)
ldf : 14 MO
yes it is small DB but before, as I did not know about backup LOG and
shrink log file, I had for the same ldf file a size of 13 Go, and this
is big.
Really thank you because I solved this problem and everything works
file now.
These information helped me a bunch. :)
Ina
Robert Klemme wrote:
> On 17.01.2007 10:26, ina wrote:
> > I have a DB that receives a massive amount of data every two days and
> > several Transaction (USP) and delete records are usually done on it.
> >
> > During these operations, the log size goes up until 32 Mo.
> What unit is that? Megabytes? If so this is really a small DB you
> should not worry about sizes in that area at all.
> > the size of the .mdf is 9Mo and .ldf is 14Mo
> >
> > The DB is set to FULL and a backup DB and LOG is performed.
> >
> > I set up the autoshink as well. is it required?
> As Uri pointed out, rather switch this off since you only waste
> performance. The log will grow and shrink anyway so you can leave it at
> the largest size.
> > Why the log file increase so much and how to set up correctly the
> > transaction log file properties?
> Because apparently you DB needs the space (you mention "massive inserts").
> Kind regards
> robert

How to set up the transaction log file properties?

Hello Guys,
I have question concerning the log file size:
I have a DB that receives a massive amount of data every two days and
several Transaction (USP) and delete records are usually done on it.
During these operations, the log size goes up until 32 Mo.
the size of the .mdf is 9Mo and .ldf is 14Mo
The DB is set to FULL and a backup DB and LOG is performed.
I set up the autoshink as well. is it required?
Why the log file increase so much and how to set up correctly the
transaction log file properties?
Thanks on advance.
Ina
ina
> I set up the autoshink as well. is it required?
No, disable this option

> Why the log file increase so much and how to set up correctly the
> transaction log file properties?
Why do you concern about that the log file is growing? That means that SQL
Server needs more virtual log files to deal with data. Make sure that you
have a free space enough for log file
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1169025984.073903.91700@.v45g2000cwv.googlegro ups.com...
> Hello Guys,
> I have question concerning the log file size:
> I have a DB that receives a massive amount of data every two days and
> several Transaction (USP) and delete records are usually done on it.
> During these operations, the log size goes up until 32 Mo.
> the size of the .mdf is 9Mo and .ldf is 14Mo
> The DB is set to FULL and a backup DB and LOG is performed.
> I set up the autoshink as well. is it required?
> Why the log file increase so much and how to set up correctly the
> transaction log file properties?
>
> Thanks on advance.
> Ina
>
|||Thanks
mdf: 9 MO (Mega Octets)
ldf : 14 MO
yes it is small DB but before, as I did not know about backup LOG and
shrink log file, I had for the same ldf file a size of 13 Go, and this
is big.
Really thank you because I solved this problem and everything works
file now.
These information helped me a bunch.
Ina
Robert Klemme wrote:
> On 17.01.2007 10:26, ina wrote:
> What unit is that? Megabytes? If so this is really a small DB you
> should not worry about sizes in that area at all.
>
> As Uri pointed out, rather switch this off since you only waste
> performance. The log will grow and shrink anyway so you can leave it at
> the largest size.
>
> Because apparently you DB needs the space (you mention "massive inserts").
> Kind regards
> robert
sql

How to set up the transaction log file properties?

Hello Guys,
I have question concerning the log file size:
I have a DB that receives a massive amount of data every two days and
several Transaction (USP) and delete records are usually done on it.
During these operations, the log size goes up until 32 Mo.
the size of the .mdf is 9Mo and .ldf is 14Mo
The DB is set to FULL and a backup DB and LOG is performed.
I set up the autoshink as well. is it required?
Why the log file increase so much and how to set up correctly the
transaction log file properties?
Thanks on advance.
Inaina
> I set up the autoshink as well. is it required?
No, disable this option

> Why the log file increase so much and how to set up correctly the
> transaction log file properties?
Why do you concern about that the log file is growing? That means that SQL
Server needs more virtual log files to deal with data. Make sure that you
have a free space enough for log file
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1169025984.073903.91700@.v45g2000cwv.googlegroups.com...
> Hello Guys,
> I have question concerning the log file size:
> I have a DB that receives a massive amount of data every two days and
> several Transaction (USP) and delete records are usually done on it.
> During these operations, the log size goes up until 32 Mo.
> the size of the .mdf is 9Mo and .ldf is 14Mo
> The DB is set to FULL and a backup DB and LOG is performed.
> I set up the autoshink as well. is it required?
> Why the log file increase so much and how to set up correctly the
> transaction log file properties?
>
> Thanks on advance.
> Ina
>|||On 17.01.2007 10:26, ina wrote:
> I have a DB that receives a massive amount of data every two days and
> several Transaction (USP) and delete records are usually done on it.
> During these operations, the log size goes up until 32 Mo.
What unit is that? Megabytes? If so this is really a small DB you
should not worry about sizes in that area at all.

> the size of the .mdf is 9Mo and .ldf is 14Mo
> The DB is set to FULL and a backup DB and LOG is performed.
> I set up the autoshink as well. is it required?
As Uri pointed out, rather switch this off since you only waste
performance. The log will grow and shrink anyway so you can leave it at
the largest size.

> Why the log file increase so much and how to set up correctly the
> transaction log file properties?
Because apparently you DB needs the space (you mention "massive inserts").
Kind regards
robert|||Thanks
mdf: 9 MO (Mega Octets)
ldf : 14 MO
yes it is small DB but before, as I did not know about backup LOG and
shrink log file, I had for the same ldf file a size of 13 Go, and this
is big.
Really thank you because I solved this problem and everything works
file now.
These information helped me a bunch.
Ina
Robert Klemme wrote:
> On 17.01.2007 10:26, ina wrote:
> What unit is that? Megabytes? If so this is really a small DB you
> should not worry about sizes in that area at all.
>
> As Uri pointed out, rather switch this off since you only waste
> performance. The log will grow and shrink anyway so you can leave it at
> the largest size.
>
> Because apparently you DB needs the space (you mention "massive inserts").
> Kind regards
> robert

How to set a bigger rollback segment?

Hi,

I′m trying to transfer a large amount of data from Oracle 8 to Sql Server. For each table, I have an OleDBSource with DataAccessMode Command (select with one inner join), Data Conversion and OleDBDestination. Sometimes I′m getting an ORA-01555 snapshot too old error, so I′d like to set a bigger rollback segment, but don′t know how. Please, can anybody help me?

Thanks

Janca

That has nothing to do with SSIS. That is an Oracle DB related issue that needs to be address for the DBA.

Whatever you are doing in the package; Have you tried to commit the SSIS work in a smaller batches? That is something you can controll.