Viewing 15 posts - 1,336 through 1,350 (of 2,897 total)
I do #1. Works well for my purposes.
June 23, 2010 at 9:20 pm
Perhaps your Netwrok Admin is running BackupExec from another server ?
Run this and look at the user_name colums for the various backups
SELECT sysdb.name, bkup.description, bkup.backup_finish_date,
case
when type='D'...
June 17, 2010 at 8:37 am
Duran (6/17/2010)
June 17, 2010 at 8:21 am
paul_jacobs (6/16/2010)
"Placebo solution" I had to chuckle at your choice of words... Anyhow, do you think the shrink database will do more harm than good?
Yes
June 17, 2010 at 5:06 am
Maybe not related, but SP3 has been out a while.
June 17, 2010 at 5:04 am
Was the document in the SQL database ? Either way, I don't see how a shrink would help.
A placebo solution would be to write 5 gig of junk...
June 16, 2010 at 3:03 pm
bigfonx (6/15/2010)
June 15, 2010 at 10:59 am
Recovery Model: Database -> Properties -> Options -> Recovery Model
Backups: Management -> Maintenance Plans -> New Maint Plan ->
- Give it a name ie "SQL FULL Backups"
-...
June 15, 2010 at 3:22 am
You can create 1 job that backs up all the databases. It will process them 1 at a time.
June 14, 2010 at 8:36 pm
Is your database in FULL recovery mode ? It should be. If not, set to FULL recovery, take a FULL backup right away, then schedule transaction log backups to...
June 14, 2010 at 10:05 am
I recently implemented a free tool called SQL Scheduler to use with SQL Internal Database (SSEE) that does not have SQL Agent. It's simple & works well, allowing me to...
June 13, 2010 at 3:13 am
There shouldn't be any impact, because no one should be using 'sa'. But if anything is using 'sa', it will fail.
When I first started at this company, 'sa' was...
June 10, 2010 at 2:18 pm
Doesn't look like you have any free space to shrink.
June 10, 2010 at 12:52 pm
Viewing 15 posts - 1,336 through 1,350 (of 2,897 total)