Yes, you can do it using sqlcmd.

Inside the script, you use the following syntax (an example from setting up database mirroring using such a script)

:SETVAR PrincipalServer (local)\SQLDev01

:SETVAR MirrorServer (local)\SQLDev02

:SETVAR WitnessServer...

Why do you keep going on about SQL Log Rescue? There is no log recovery tool on the market that copes with everything in the SS2005 transaction log.

What are you...

Very interesting - and who do you work for? Looks a bit like advertizing to me.

I've seen many of these come and go while in the SQL team - rarely...

ok - so you can either take (and continue to take) log backups and stay in full recovery mode, or you can change modes and run a dbcc shrinkfile on...

Take a look at this blog post I wrote on just this problem - it'll tel lyou the options and how to go about them - http://www.sqlskills.com/blogs/paul/2007/09/24/SearchEngineQA1RunningOutOfTransactionLogSpace.aspx

SQL Server 2005 doesn't recommend using REPAIR_FAST... I removed the REPAIR_FAST functionality when I rewrote DBCC CHECKDB for SS2005. If you look in Books Online you'll see that the option...

I threw together a quick list on my old blog at http://blogs.msdn.com/sqlserverstorageengine/archive/2007/04/30/very-quick-list-of-vldb-maintenance-best-practices.aspx.

Primary in my mind would be making sure you have the ability to recover in a disaster - both...

Minaz - your advice would be correct if Nicola was running SS 2000 but she's on SS 2005, so page checksums and SQLIOSim are the way to go.

Yeah - I just wanted to point Nicola right to what I would do first.

Given that the corruption problems keep happening after they fixed it by restoring from a backup, I'd guess you have a hardware issue. Even though the hardware checks out -...

Interesting - did you get any helpful messages in the error log or just the usual one about insufficient resources or inaccessible files?

One more thing to bear in mind is that a log reader's undo functionality will only work as long as the reason you're going back in time is not physical...

As long as your transaction log is not corrupted, you should be able to do a point in time restore to just before the corruption occurs.

In a nutshell, here's what...

Is your database attached still or not?

If so, you'll need to build a new transaction log. See my advice in previous thread I replied to.

If not, you'll need to use...

If you've lost the .ldf file and all you have is a backup from 15 days ago, you have two options:

1) restore the 15-day old backup and lose the last...