Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Beginning Administration


Beginning Administration

Author
Message
Courtney Rabuffo
Courtney Rabuffo
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 20

I would definitely be interested in getting some basic information on SQL admin duties. Specifically maintenance plans, security, & optimization.





ckentebe
ckentebe
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 1

I am definitely interested in the Security and Administration duties of a MS2000 DBA.




Christopher B. Kentebe
B.S.E.E., O.C.P.
Microsoft SQL Server2000 DBA
Phone : (416) 338-1274
Fax : (416) 696-3765
Email: ckentebe@toronto.ca
LN-202212
LN-202212
SSChasing Mays
SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)SSChasing Mays (633 reputation)

Group: General Forum Members
Points: 633 Visits: 393

This should help set something up. This article provides some structure. Hope it helps.

 

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops4.mspx#ECAA


Phil Henry
Phil Henry
Grasshopper
Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)

Group: General Forum Members
Points: 18 Visits: 298

Im administrator of an MIS that uses  SQL 2000 - and while I can find my way around the db, create backups, use dts,  and write Crystal Reports from the data - I find it difficult to understand  how to create views ( so that my Crystal Report can report from the view rather than a group of tables.)

eg: I failed miserably at replication ( so I took my ball home and refused to play anymore!)

Im also at  a total loss to understand  'joins' -  the concept, how they work/how to use them  etc etc

 

Any Steve Jones style prompt sheets would be greatfully appreciated


David Thayer
David Thayer
SSC-Enthusiastic
SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)

Group: General Forum Members
Points: 128 Visits: 1

The first thing a good dba should do, coming into an existing environment, is to put together a backup scheme.  Typically, a full backup once a week, and transaction logs more often (depending on how your organization would view data loss in a DR scenario).  Secondly, maintenance plans, DBCC checks, reindexing, etc.  Some good ones to check out are DBCC CheckDB, DBCC Reindex, DBCC IndexDefrag, DBCC ShowContig.  Some of these are very intrusive and should be done off-hours.  Capacity planning is also important.  Monitor your db sizes and keep tabs on it.  Once you have all of these automated, then you can start getting your hands dirty with performance tuning at the query level, DTS, Replication.

 

Getting back to backups, be sure to test your backups on a regular basis.

 

 

 


David Thayer
David Thayer
SSC-Enthusiastic
SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)

Group: General Forum Members
Points: 128 Visits: 1

A DBA tale

Bob walked into his new office with overwhelming confidence as the exiting DBA finished packing his belongings. As Bob walked into the room, the DBA stopped a moment, walked to his desk, took out three envelopes and handed them to Bob.The exiting guy told Bob not to open them, as they would only be effective if they were opened at the right time. Bob asked when that would be, and the exiting DBA said that, when a situation came up where you don't know what to do, open #1 before you walk in to talk to the boss.

Bob got busy and got into the work, handled everything that came his way until one day, he was asked to get some data from a backup. Bob found out that his backups were failing. Bob remembered the envelopes, tore open #1 which contained a slip of paper which read "Blame it on the last DBA". Bob walked into the office wondering what to say and thought of how easily it could have been avoided. He checked the SQL Mail setup, even tested it! How was he to know that MIS would change something in the mail setup? Of course, to blame them would incur the wrath of the MIS department, and being a newbie, he didn't want to do that, so he blindly took the advice in the envelope. His boss agreed that it was the fault of the previous DBA, but told Bob that all SQL Server issues were his problem from now on. Bob learned from his mistake and set up SQL Mail to send him email upon success AND failure of any job. This way, if he didn't receive an email, he'd know there was a problem.

 

Two weeks went by, and Bob was a legend in his own mind. He loved the new backup strategy he'd implemented. It was so sleek and flexible, there was no way he'd lose data. Then, it was put to the test, and the recovery operation failed. He'd had successful emails regarding his backups and couldn't understand how this could happen. Was it the drive or the server??? He had no idea why he couldn't restore from his backups. Then he remembered the envelopes. Tearing open the second one, it said, simply "Blame the hardware." This was a great revelation to Bob. He'd never tested his recovery plan from start to finish, and never restored a backup in test before going live. Bob went to his boss and told him it was the hardware. The boss agreed, but pointed out that the company had just lost 48 hours worth of work. Bob left, with his tail between his legs. Bob learned that it's important to test your recovery plan.

He was just about to turn in his resignation when he realized he had another envelope. It couldn't possibly help him feel better about the hole he'd dug for himself, but what had he to lose? Bob opened the last envelope, read the note, and smiled. "Create 3 envelopes, label them #1, #2, #3, and create notes that say "Blame it on the last DBA", "Blame the hardware.", and in the third envelope place this note, and start looking for a new job. You're the only one to blame."


TIMOTHY A. JUMONVILLE
TIMOTHY A. JUMONVILLE
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 8
I'M NEW TO THIS...

HAVE MSACCESS DATABASE SPLIT INTO DATABASE AND DATABASE_BE. GETTING TOO BIG FOR ACCESS. WANT TO PUT THE BACK END INTO SQL SERVER AND USE THE FRONT END TO MANIPULATE, ETC.

HOW DO I GET THE BACK END INTO SQL SERVER?

THANKS =)
Frank Kalis
Frank Kalis
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 5971 Visits: 289

http://msdn.microsoft.com/sql/default.aspx?pull=/library/en-us/dnsql2k/html/sqlbackend.asp

http://www.support.microsoft.com/?scid=kb;en-us;237980

http://support.microsoft.com/default.aspx?scid=kb;EN-US;884457

http://support.microsoft.com/default.aspx?scid=kb;EN-US;241743

should get you going. A search here in the fora might also be helpful.



--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/
David Thayer
David Thayer
SSC-Enthusiastic
SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)

Group: General Forum Members
Points: 128 Visits: 1
Pretty easy to DTS the data into your SQL Server and link to it through Access (ODBC).
mikal r. pippins
mikal r. pippins
Grasshopper
Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)

Group: General Forum Members
Points: 10 Visits: 16
Better do it with a copy first when you have plenty of free time. Things are about to get real different.


We have met the enemy and he is us.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search