Carl Federl (4/22/2010)

Do you mean the size of the database log file ( ldf extention) or the...

pshaship (4/22/2010)

why only...

Largest is 4.9Gig

I have 2000, 2005 Ent and 2008 Ent.

Thanks for the suggestion on how to do reindexing but I still have the problem. It is very important in my enviroment to find a solution to this problem.

Yes I do. This is only a problem with logshipping databases. I only have 4mb line to offsite.

I think I saw something once that said if some backup is running...

Sorry here is the full select

use master

select * from sysprocesses where spid > 50 and program_name like 'SQLAgent - TSQL JobStep%'

Hi

The next step is to check the sysprocess table. Look for something like "SQLAgent - TSQL JobStep............" ...

Try this script and see if the job is still in the table:

select * from sysjobs

What kind off condition are you looking at. Here I am thinking that there could...

The log files growth is the same as when it is in full mode. I see logfiles that grow up to 18 gigs in one hour while reindex is happening.

Hi

For the sp that use the table you can run the following script.

select name from

sys.sql_modules join

sys.objects on sys.sql_modules.object_id =

sys.objects.object_id

where definition like'%tablename%'

order by name

1. Where did you setup the Alert?

2. What version suppose 2005

3. Check - select * from sysalerts in msdb

4. Is it perhaps logshipping

Add step to the Reindex job to run logshipping backup job and then you can use DBCC shrinkfile to shrink the log file. You can also put the DB in...

Hi

I found the answer after a bit of trile and error.

thanks

Thanks for the work around. Must be some kind of MS bug.