Your replsys output looks fine to me, too. What OS and OS service pack are you on?

Also look at sqlsp.out for clues. Two common causes for sp4 install failure are...

Trailing blanks are ignored in varchar comparisons, and DISTINCT and UNIQUE both follow this behavior:

create table #junk

(crap varchar(10) not null)

insert #junk values ('xxx')

insert #junk values ('xxx ')

select distinct crap from...

Variables of the datatype TEXT are not supported in SQL Server 2000, although the engine seems to accept them as parameter declarations. How are you calling this procedure? My guess...

Sounds like a lot of work!

For the larger tables, I would suggest using DTS to create a file on the SQL Server machine, and then either bcp in the file...

Look in the file replsys.out for clues.

use pubs

go

create table #junk

(

Name nvarchar(20),

Rows char(11),

reserved varchar(18),

Data varchar(18),

index_size varchar(18),

Unused varchar(18)

)

insert #junk exec sp_spaceused @objname = 'authors'

insert #junk exec sp_spaceused @objname = 'titles'

select * from #junk

Check out the Xfind script at:

http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=1124

Check out the Xfind script at:

http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=1124

You may want to download sp4 again. The error is a sql syntax error during a create procedure statement. Perhaps the script got corrupted.

Yes, rapid transaction log growth can be the result of implicit transactions, but such transactions are not necessarily "lousy sql". A single, simple insert-select query from a large table might...

I wonder if there is actually that much log activity, or if some process is attempting to maintain the log at a fixed size.

Try:

BACKUP LOG INFOPROD TO DISK = N'D:\MSSQL\BACKUP\INFOPROD_tran_test1.bak'...

One more caution: hardware failures can result in gradually worsening corruption, which may not be noticed right away. This can create a situation where seemingly successfully completed backups will actually...

What sort of help are you looking for? homebrew01's suggestion to create database maintenance plans is a good place to start. I would make the following recommendations regarding them:

1. Create...

SQL Server and Agent use different email sessions. If I remember correctly, a tech net article explained that the reason for hung email sessions was that the client displays a...

Using bcp out to a file and a BULK INSERT back in to Table A is a good suggestion. Also good is the suggestion to put the transaction logs on...