Hi,

I had the exact same problem..did u find any solution for this ?

Thanks

Santosh

Hi,

I would have started with basics such as

1)Check the startup account for pasword expiry or account lockout

2)Check that id is part of local administrator

3)try starting it from commanda prompt. that...

Hi

It seems to me more like the backup files are getting appenend As a result the physical backupfile is bigger than the size in backupset

Thanks and Regards

Santhu

Hi There are two ways to do it

1)If it is a sql agent job.you set the startup option in job schedule on to run at startup

2)If you have a procedure...

Use XP_cmdshell 'dir <full path>'

Check if it that gives any error

Santhu

Hi,

You can not move the datafile to different file group. Instead you can identify the biggest table and move that table to different filegroup, thus freeing up space in the...

Why not try backing up manually using TSQL and see what error it throws ?

Santhu

Try sending some Test mails. Then run the below query and post the results

select * from msdb..sysmail_allitems

Thanks and Regards

I am interested at looking at indexf ragmentations. Please run the below query and post the results

select b.name, b.type, c.name, a.*

from sys.dm_db_index_physical_stats (db_id(), 0, null, 0, 'SAMPLED') as a

join...

Well,

This rules out the logspace issue for good.

Santhubt

yes, Thats true. U can use either

DBCC sqlperf(logspace) to check logusage. To be more specific can run the below query

use <database Name>

go;

select name,filename,size/128"Actual Size",maxsize/128"Maxsize",fileproperty(name,'spaceused')/128"spaceUsed" from sysfiles

Thanks and Regards

Santhubt

I believe , after sql restarts it would not try to recover the database as it referes the db_status from sys databases.

Otherwise most of the secondary databases in logshipping ,...

I don't see any reason why the replication be affected, by re-configuring log shipping. I think there should not be any issues.

Thanks and Regards

Santhubt

I Agree with Ignacio.

Once you have a log shipping, log backups are already taken care. Regarding Logfile being 170GB, u could check log usage within that file.

Thanks and Regards

Santhubt

I suggest you to use VB scripts and schedule it using windows scheduler in any of the central server. If you have multiple server to monitor, pass the server list...