Showing posts with label size. Show all posts
Showing posts with label size. Show all posts

Friday, March 9, 2012

Keeping the transaction log small during initialization

How do I keep the transaction log small during initialization of a
subscription. The size of the transaction gets to be at least four
times the size of the data and fills up the hard drive.
Is there a way to initialize the database without keeping the
transaction logs?
I can't seem to truncate and shrink during initialization either.
Any help is greatly appreciated.
Michael Swart
There is no real way to do this, other than a no sync subscription, or to
kick everyone off your publication database while you generate the snapshot.
You might also want to run DBCC Opentran to see if there are any open
transactions which are causing your tlog to balloon.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Michael Swart" <mjswart@.yahoo.com> wrote in message
news:22f04e15.0408040512.115202ca@.posting.google.c om...
> How do I keep the transaction log small during initialization of a
> subscription. The size of the transaction gets to be at least four
> times the size of the data and fills up the hard drive.
> Is there a way to initialize the database without keeping the
> transaction logs?
> I can't seem to truncate and shrink during initialization either.
> Any help is greatly appreciated.
> Michael Swart

Friday, February 24, 2012

Keep section of report the same size

I need to keep a section of a report the same size. I have now a table with a detail and group section. The table header must print on every page and the table footer must print on every page. The detail section can only be 16 rows. When I have more than 16 rows the report page breaks perfectly and puts the remaining rows on the next page along with repeating the header and footer. The problem is when there are fewer than 16 rows the table does not take up the full page and looks horrible. All my displayed data is in the data set. I have looked at padding the dataset with bogus rows that would show up at the end and just not display but would rather take care of this on the report end. Any ideas?

Thanks, Chad

Hve you tried placing the table in a rectangle control and setting it's size? I believe it can grow if it needs to and uses the defined size as it's minimum.