only a few dozen tables out of the database - gotta be replication.

..or you use the new replication model steve has just patented 🙂

bwillsie, you just made my point. You are trying to use log shipping, which is primarily designed as an HA solution. for reporting purposes, which is just a handy byproduct...

steve, I think you just reinvented transactional Replication!

I think we are in danger of over complicating things. People need to decide whether they want to use their databases copies for...

dbcc shrinkfile has not been deprecated.

Not quite sure from your post but if your db has more than one log file get rid of the second one using dbcc shrinkfile...

use with standby option

stoviber (2/22/2010)

My big gripe at the moment is the size of the database, circa 300GB meaning any recovery wont be quick and when I start looking at replicating the database...

Stevie, if not already doing so sounds lie you would benefit from cutting down\spreading out the reindexing you are doing. If you search BOL for sys.dm_db_index_ physical_stats that entry comtains...

:crying:

did the points from timewarp get reinstated?- I lost track.

Rule of thumb -

snapshots for reporting databases

mirroring and logshipping for High Availability or DR

replication for scale-out (data available in more than one place).

Thats not cast in stone thats what...

good to hear, it can just be a case of timing sometimes

If SQL started using the third log file it obviously needed it so perhaps getting rid of it might not be a good idea, SQL might need the space again.

that...

In SQLAgent you can schedule jobs to run only when CPU is idle (you define what you mean by idle)

a restore from a .bak file will create the database files for you, but the directory structure needs to exist.

run restore filelistonly from disk = 'wherever' to see where the...