If you are using Enterprise Edition you could create a snapshot of the subscriber, load the data warehouse from the snapshot, and drop the snapshot when the load is finished....

Try looking at the msdb.dbo.backup___ tables. They will have the name of every backup file written, the first & last LSNs.

The backup history in the tables should go back...

I used to do backups over a network that would take at least 4.5 hours for a 200GB database. The target storage device had some idiosyncracies that I won't...

You definately need to know all the details. Even on a SAN you need to worry about putting data files, log files, and tempdb on separate physical disks. ...

Now, for the bad news. Varchar(MAX), NVarchar(Max) and VarBinary(Max) do NOT get stored on the data pages. They are always stored in a different type of page than...

How about using the -o argument to specify the output file?

DECLARE @cmd VARCHAR(255)

set @cmd = 'OSQL -E -Q "Select filepath, filetree, filename from ccs.dbo.Work_DBA_Purge" -O -o T:\temp\myfile.txt'

EXEC xp_cmdshell @cmd

You could shorten that to "IF APP_NAME() != 'MyAppName'", which would probably be better than directly referencing the sysprocesses compatability view.

The most interesting part of this process to me is creating the script to restore all the databases after you've figured out how to zip, copy, and unzip the backup...

I agree that only being able to do backups to tape is a bad situation. Since you don't have room to restore a copy of the database, your only...

In SQL 2005 you would have a much easier time attacking this problem with Integration Services. But if you're stuck with SQL 2000, here's one way.

1 Write a SQL...

WinZip Pro costs a whopping $50. (The Pro version is needed to use the command-line addon). It can create self-extracting files, so you only need to pay for...

If you pay for a registered copy of WinZip you can get the command-line addon which would happily process multiple files. It is very inexpensive, but I believe there...

All data is stored on disk, and switching to varchar(max) will not affect any select or update or backup/restore statements.

If you're really interested enough to read about how it is...

I would try using brackets to quote database, table, and index names instead of quotes. The sp_defragment_indexes procedure you reference uses RTRIM(@objectowner) + '.' + RTRIM(@tablename), which will fail...

To elaborate on ALZDBA's solution a little to make it clear what he was proposing:

select facilityname

, sum(case when condition1 then 1 else 0 end ) as whatevernameyouwannegiveit

, sum(case when condition2...