@sudhakar -

Any patches or hotfixes applied on the server.

Ref.

http://social.msdn.microsoft.com/Forums/en-US/sqltools/thread/006e8e8d-a9c4-4dd4-8949-d3f8e9001bb7/

http://sqlserver-qa.net/blogs/perftune/archive/2007/10/01/2284.aspx

[font="Verdana"]@Basit - There are all possibility that the jobs failed or log sequence was broken.Assuming that you have already stopped the log shipping what ideally you should do is take...

[font="Verdana"]****Please change name of the database before executing the script*****

Use 'Database Name'

go

SELECT

'EXEC sp_change_users_login ''Update_One'', ''' + su.name + ''', ''' + su.name + ''''

FROM

sysusers su

LEFT JOIN master.dbo.syslogins sl...

Use this instead

sp_rename 'Db2..Tmp_table', 'Db2..table'

Njoi SQL'ing

[font="Verdana"]There are couple of ways to do it.

1. Textbook Way- sp_cycle_errorlog - Closes the current error log file and cycles the error log extension numbers just like a server restart....

Full backup will backup committed data....it will be a wise decision to take log backups and restore on other server however the possibility is still that the copy that is...

Check the Utilization% of the file.

And in-case if there is some space you can check if there is any active or sleeping SPID on the db if yes then...

Try using the "With Init" clause

E.g

Backup database DBName to disk = '' with init

,stats=10

yeah that's true ....My apologies I forgot the log backups option...let me re-correct ...A weekly full backup followed by a daily differential backup and log backup(10-15 min or more depending...

It completely depends on your strategy.If resources are not a constraint a Weekly full and followed by daily differential is enough. Also you should possibly look at table partitioning and...