How To Get Rid Of Sql Log

Hi,
I have a Data base on Sql Server 2000, sp3a. Database is used to to build summary tables to show reports on web. There are many sub systems, which prepare summarized tables for faster web page serving. Every thing is working fine.

The problem is sql server log gets full. In one given day it could go up to 18 GB. I know, if I back it up it gets truncated. Is there a way, I can stop sql server not to log, as it is not needed?

Can I set up Sql server to automatically truncate it. I do have auto shrink options checked, but log file still keeps growing.

Any idea, what is going on here.
Thanks,
Mashro::Is there a way, I can stop sql server not to log, as it is not needed?

You err, it IS needed.

Read up in the documentation what the log is used for. It is needed.|||Back it up regularly to keep it from growing out of control. You can't eliminate the log. It's a pretty key piece of the puzzle. If you have the db set to simple recovery, it should truncate the log on each checkpoint. Probably no need to use a full recovery model on a 'derived' reporting database like you seem to have.

How to get non-fixed-width results in xp_sendmail?

(SQL Server 2000, SP3a)
Hello, all!
I'm using xp_sendmail with the @.query parameter and a @.separator of ', ' with an
attachment.
The query works out great -- but all of my string data is "fixed width", with spaces at
the end of them when I look at it in Excel. (Like it was CHAR(X) instead of VARCHAR(X).)
I've verified that the table is what I think it is (using VARCHARs). I think this is just
a function of xp_sendmail and an attachment. Is there any way to get rid of this
fixed-width artifact?
Thanks!
John PetersonThere's an alternative to SQLMail you might like to consider :-
http://www.sqldev.net/xp/xpsmtp.htm
--
HTH
Ryan Waight, MCDBA, MCSE
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:es$hDVhrDHA.360@.TK2MSFTNGP12.phx.gbl...
> (SQL Server 2000, SP3a)
> Hello, all!
> I'm using xp_sendmail with the @.query parameter and a @.separator of ', '
with an
> attachment.
> The query works out great -- but all of my string data is "fixed width",
with spaces at
> the end of them when I look at it in Excel. (Like it was CHAR(X) instead
of VARCHAR(X).)
> I've verified that the table is what I think it is (using VARCHARs). I
think this is just
> a function of xp_sendmail and an attachment. Is there any way to get rid
of this
> fixed-width artifact?
> Thanks!
> John Peterson
>|||Thanks, Ryan!
But, this alternative doesn't yet support the @.query type of operation, which I'm
currently relying on.
It seems to me that there ought to be *some* way to prevent the output from being in
fixed-width mode -- but for the life of me I cannot figure it out...
"Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:O$Z7XOorDHA.1184@.TK2MSFTNGP10.phx.gbl...
> There's an alternative to SQLMail you might like to consider :-
> http://www.sqldev.net/xp/xpsmtp.htm
> --
> HTH
> Ryan Waight, MCDBA, MCSE
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:es$hDVhrDHA.360@.TK2MSFTNGP12.phx.gbl...
> > (SQL Server 2000, SP3a)
> >
> > Hello, all!
> >
> > I'm using xp_sendmail with the @.query parameter and a @.separator of ', '
> with an
> > attachment.
> >
> > The query works out great -- but all of my string data is "fixed width",
> with spaces at
> > the end of them when I look at it in Excel. (Like it was CHAR(X) instead
> of VARCHAR(X).)
> >
> > I've verified that the table is what I think it is (using VARCHARs). I
> think this is just
> > a function of xp_sendmail and an attachment. Is there any way to get rid
> of this
> > fixed-width artifact?
> >
> > Thanks!
> >
> > John Peterson
> >
> >
>