Log Shipping is fairly easy to script out yourself as well.

You can find several homegrown log shipping scripts online that perform the same functionality however do not require enterprise edition...

Standard compression utilities typically have problems with files larger than one or two gigs. Simply try to run a huge file through winzip and not only will it take...

Rather than using DTS to copy data to a "backup" file, I would recommend using SQL's builtin backup functionality. Combining full and transaction log backups into a backup strategy...

You also may have a huge transaction log. A full backup takes a backup of the data file and the transaction log. TLogs should never grow as large...

Even though its on a shared network make sure that you have permissions to the network drive and folder that the backup file sits in.

You can try an xp_cmdshell 'dir...

Not that I know of... the best way to reduce restore time is to get faster disks on your data drive subsystems. Either faster disks or more disks on...

LiteSpeed also has their own enterprise management console that allows easy restores of protected backup files.

One thing to keep in mind with native password protected backups. Even though the...

You should be able to either remove it via add/remove programs or you can do a system rollback.

Imceda Software has a product called Speed IDE that does exactly what you are looking for.  You can put any object in your database (sp's, table schema, permissions, views, etc...)...

Sounds like you've got a corrupted data file.  You should consider restoring your most recent backup to rectify the problem.

You should be able to just kill the process.  I've killed backups several times in the past with no ill effects.

You can also parse through the SQL Server error logs to check for failed backups. If a backup or restore operation failed, an entry will get written into the...

Here is a link (from 1 year ago) that documets the largest databases sitting on SQL Server.  While this is a year old and I personally know of many more...

Don't you specify port number in the .opt file that TDP uses.  I think there is a *.opt file that includes connection strings used to specify how the client connects...

I use procedures similar to the ones listed above.  Be careful if you use maintenance plans to delete old files.  I've found the way they do it to be fairly...