I'm trying to figure out how you ended up with a 91GB log for a 1GB database. I'm guessing it was in full recovery and never had a log backup?
The first suggestion I would have would be to restore this database on a server with enough space for the log, back up the log, and then shrink it. You should then be able to back it up and have a reasonable package to restore on your laptop.
If that is not possible for some reason, your only option would be to put the database in emergency mode and mine it for data. (in other words, read data out of it into an empty database. It won't be updateable in emergency mode.)
Hi Kevin,
The DB is a Customer BD and they sent it over recently, just before the System Admin went on holidays. I guess the Tx log is never shrunk, therefore holding 91 GB of Log. Since there is no easy way around restoring the database on my current configuration, I'll get an external Hard-disk, format it as NTFS, and then put all the data back on-line before shinking the Log and moving it all back to the laptops hard-disk.
Regards.