Viewing 15 posts - 181 through 195 (of 210 total)
I suppose its possible they created this job in order to protect against a failed backup. Perhaps if a full backup failed, their log would fill up before the next...
December 1, 2004 at 10:29 am
LiteSpeed for SQL Server (from Imceda software) supports object level recovery. Using this product you will be able to restore individual tables from a full backup file (native or compressed...
November 28, 2004 at 8:45 pm
The only issue I have run into when upgrading from Win 2000 to Win 2003 is regarding the OLEDB.dll driver not being correctly upgraded. This typically only reers its ugly...
November 23, 2004 at 3:17 pm
I'm not very familiar with Double-Take but I believe it is an implementation of snapshot technology.
Snapshot technology as a whole is fantastic for high availability and for instantaneous backups, however...
November 23, 2004 at 3:11 pm
Definitely sounds like a hardware issue associated with the drive you are reading/writting from. Is it possible to try writting to a different local drive on a completely different drive...
November 23, 2004 at 3:04 pm
Most likely this is because your database has 75 gigs allocated to it. If you have 75 gigs allocated for your tlog and data file, when you restore it will...
November 23, 2004 at 3:01 pm
If you don't want to backup using drive mappings you should use UNC path naming conventions. SQL server handles these much better than mapped network drives. All you need to...
November 23, 2004 at 2:34 pm
Make sure you see if your TLog file is configured to autogrow. Even though this causes MAJOR performance hits if you reach this threshhold, it will atleast not cause a...
November 22, 2004 at 5:37 pm
One way that I've used is to include a datetime stamp in the filename and then delete the files based on parsing out the filename from the file then doing...
November 22, 2004 at 5:31 pm
Be careful with Profiler. Microsoft has stated that they cannot guarantee that all transactions are captured with profiler. Especially during periods of high activity, some transactions may be lost. If...
November 22, 2004 at 5:24 pm
Scott,
You should look at log shipping solutions. These are very simple to set up and do a good job of keeping databases in sync within a specified time interval. Log...
October 29, 2004 at 5:23 pm
It looks like your referring to the LiteSpeed simple log shipping scripts. We do not provide a procedure called sp_logship but do have simple log shipping scripts and an @hourduration...
October 29, 2004 at 4:23 pm
SQL Server is real picky about how it handles mapped drives. I've found that the easiest way to handle network drives is to use UNC naming conventions. Even...
October 28, 2004 at 10:51 am
I believe the scenario is that during a full backup first the .MDF file is backed up and then at the end of a full backup a log backup is...
October 28, 2004 at 10:00 am
The product has actually just been acquired by Imceda Software and has really taken off. Please look to http://www.imceda.com for more info.
October 12, 2004 at 7:25 pm
Viewing 15 posts - 181 through 195 (of 210 total)