January 15, 2009 at 9:20 am
David Reed (1/15/2009)
Wayne West (1/15/2009)
Old habits die hard. I spent my formative years as a DBA in a 4.21/6.5 environment where you did everything by hand. It warn't like them fancy gewgaws and wizards them young kids got now! GET OFF MY LAWN! 😀Um, Wayne. You're standing in the neighbors' yard. It's time to come back inside and take your meds. 😛
Seriously, though, I'm with Mr. West. The only thing that I might use the wizards for would be to generate a script, or create objects in a dev environment that I script out. All T-SQL to be run in production is subject to review from source control (several times by me and several more times by others) BEFORE it's executed anyway... right?
But I live in an apartment complex, the yard is community property! Maybe I took my wife's meds this AM by mistake.... :hehe:
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
January 15, 2009 at 9:32 am
Review? Source Code? It's this point and click?!?!? 😛
The only place I used maintenance plans is when I don't have time to set something up or someone has installed their own instance and needs something setup. Easier to get them to do a maintenance plan at first and handle things rather than nothing.
January 16, 2009 at 10:59 pm
don't mind maintenance plans for backups, they do those fairly well. I do not like them for DBCCs, and it seems that most of the maintenance plans that I see people want them to do everything. That's fine, as far as it goes, but I want more details. I do full DBCCs every work night on everything (sp_msforeachdb, except for one server) via OSQL and send the results to a text file. I have an aging system to keep the last ten runs. I then pipe the results through Find looking for "errors" and that file is grabbed by a nightly Perl script so that I see a couple of dozen lines of DBCC results rather than thousands of lines. If I see non-zero numbers in that result set, I can probe deeper into the full file that's on the server.
Steve Jones - Editor (1/15/2009)
Review? Source Code? It's this point and click?!?!? 😛The only place I used maintenance plans is when I don't have time to set something up or someone has installed their own instance and needs something setup. Easier to get them to do a maintenance plan at first and handle things rather than nothing.
Wayne,
Just to help you right. By salted (remember I am an Afrikaans (Dutch) speaking South African) I actually meant knowledgable or trained. Salted is a word we Afrikaners use to say that and not old or aged. Would you guys mind to post some of these scripts that you use and how do you schedule them to run on their own. I don't see you sitting their every night running all these scripts. Please help a wannabe DBA out will you or refer me to an article on SSC where I can learn that.
I'll appreciate that very much.:alien:
:-PManie Verster
Developer
Johannesburg
South Africa
I can do all things through Christ who strengthens me. - Holy Bible
I am a man of fixed and unbending principles, the first of which is to be flexible at all times. - Everett Mckinley Dirkson (Well, I am trying. - Manie Verster)
March 10, 2009 at 2:39 pm
Manie Verster (1/16/2009)
... Just to help you right. By salted (remember I am an Afrikaans (Dutch) speaking South African) I actually meant knowledgable or trained. Salted is a word we Afrikaners use to say that and not old or aged. Would you guys mind to post some of these scripts that you use and how do you schedule them to run on their own. I don't see you sitting their every night running all these scripts. Please help a wannabe DBA out will you or refer me to an article on SSC where I can learn that.I'll appreciate that very much.:alien:
Manie, sorry for the lack of a reply. I worked three days in the month of February: out for carpal tunnel surgery, then came back and caught pneumonia! Just now getting back to working full-time and I'm supposed to be on light duty.
I would be happy to show you some stuff, but I'm not certain how soon I can get to it. I just wanted to let you know that you're not forgotten.
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
October 30, 2013 at 8:49 am
Risky Backup:
I believe that backups written to the same file does create a single-point-of-failure; with a little work, backup scripting can create a date\time backup file to differentiate each backup file and is a lot easier to manage and restore. I have done appended file writes for reporting and error tracking in the past but for backups, such as database backups, I do recommend a separate backup file unless the loss of the backup file is a acceptable risk.
Harvey Wigfall
MCDBA
October 30, 2013 at 9:33 am
This seems to be a holdover from the old days, when servers had local disks, tape drives, and tapes were expensive. And of course, backup tapes were often un-readable. But if Microsoft had removed this 'feature', there would have been howls of protest of how it will break backup jobs 🙁
October 30, 2013 at 9:41 am
I used to use the maintenance plans but they never removed the files when they aged, I had to script something to do that. Then i found Ola's maintenance plans and used them until we switched to DPM. (ola.hallengren.com)
October 30, 2013 at 10:14 am
There is enough risk in this business if you do things simple and right. To introduce further risk into the mix is not necessary. In the old days the Ancients use to say Kiss = Keep it Simple Stupid. To over complicate this is to Keep it Simply Stupid. 🙂
M.
Not all gray hairs are Dinosaurs!
October 30, 2013 at 4:50 pm
Miles Neale (10/30/2013)
In the old days the Ancients use to say Kiss = Keep it Simple Stupid.
BWAAA-HAAAAA!!!! Since you're a fellow "Ancient", I strongly suspect you preserve the original meaning, as do I. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
October 30, 2013 at 5:03 pm
From the article:
I know that some people like having the same filename every day as it makes restores simpler, especially if they've scripted things.
I realize this is a 4 year old article but backups are the second most important thing there is in SQL server.
Not to be confused with "simple" and as Granny used to say, "I've found that people that take certain shortcuts frequently get mud in their shoes". 😉 If someone takes a "shortcut" on backups, they get what the deserve... failed restores.
So, no... I don't believe that you have a jaded or out of date opinion on this... even 4 years later.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 10 posts - 46 through 54 (of 54 total)
You must be logged in to reply to this topic. Login to reply