Viewing 15 posts - 946 through 960 (of 2,900 total)
1) Stop shrinking the database ... it's causes fragmentation & poor performance including when the database grows back to the size it needs to be.
2) Take frequent log backups,...
April 12, 2011 at 10:32 am
Sqlsavy (4/12/2011)
failed with the following error: "The transaction log for database 'SharePoint_Collab1' is full.
I usually run transaction log backups in between index rebuilds.
Read: Why is my transaction...
April 12, 2011 at 8:07 am
What service pack are you on ? There were maintenance plan bugs that were fixed in SP3
April 12, 2011 at 7:21 am
keepintouch2b (4/11/2011)
For SQL Server 2008 or Denali, I...
April 11, 2011 at 7:23 pm
Sounds as though you want to use the restore function to manipulate data ... that's the opposite of it's purpose. A restore is designed to bring a database back to...
April 11, 2011 at 1:32 pm
Step 7 sounds like you want to apply an old transaction log backup to a newer database. That won't work, or am I misunderstanding ?
April 11, 2011 at 12:08 pm
Probably some other process has a lock on the index. Are you running the maint plan during off-hours ?
April 11, 2011 at 11:47 am
Basically, the transaction log contains the database activity that has occured since the previous backup (full, diff or tran log)
Proper explanations & details here:
April 11, 2011 at 5:02 am
I think the total size of you t-log backups should be about the same. One huge daily backup, or many small 20 minute backups.
April 11, 2011 at 4:51 am
And if only have SQL Express, you can use shareware SQLScheduler to create jobs.
April 11, 2011 at 4:33 am
Our production transaction logs are backed up every 15-20 minutes.
The frequency is determined by your businesses allowable data loss.
Transaction backups once per day means you have the potential to lose...
April 11, 2011 at 4:21 am
Why do you use 2 different accounts on the forum ? I see others do it once in a while .... seems confusing all around.
April 10, 2011 at 10:22 pm
If it is a production database I would suggest something like:
1) Set to FULL recovery model
2) Take one-time full backup now to re-establish log chain
3) Take full backup daily
4) Schedule...
April 8, 2011 at 10:18 am
I assume you checked the obvious that your variable for the database name is long enough ?
The truncated name is 50 characters long.
April 7, 2011 at 2:59 pm
Viewing 15 posts - 946 through 960 (of 2,900 total)