Best Practices?

Question

Post reply

Best Practices?

PompeyTID

SSC Veteran

Points: 239
More actions
March 9, 2005 at 8:34 pm

#88281

Hi,
I've just taken a new job and inherited a complete hornets nest of sql database. The previous, ahem, DBA's did not schedule any kind of routine maintenance.
Therefore, please could somebody direct me/advise me as to what the best practices are regarding performance tuning, truncating logs, shrinking databases, checking integrity, and other basic stuff.
Thanks in advance,
Jules

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

philcart SSC-Forever Points: 47794 More actions · Answer 1

This is a pretty good start,

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx

And while not totally appropriate in some situations, the MS Best Practice Analyzer has it's uses.

http://www.microsoft.com/downloads/details.aspx?FamilyId=B352EB1F-D3CA-44EE-893E-9E07339C1F22&displaylang=en

There's really no "official" best practices. Often what one company sees as best practice, another sees as a hinderance. eg: When I started at one company, there suite of over a dozen applications all used sa to connect to the servers To apply a "best practice" of not using sa would have put them out of business because of the re-work required. (I must add that this role was the shortest in my career. I moved on pretty quickly once I uncovered the snake pit )

Generally what has worked for me in my various roles is cobbling bits together as they apply to the company I'm working for. A quick "google" for SQL Server Best Practices will give you a wealth of information to pick and choose from

--------------------
Colt 45 - the original point and click interface

Greg Norris-214114 SSC Eights! Points: 888 More actions · Answer 2

Just chimming in...

Thanks Phil. I'm in a similar situation. New job, but only a non-poisonous-snakepit (I hope).

Looking for best practices from a developer's perspective. To much code to write & not enough reading time. I hate discovering a week after I've finished a project that something I did should have been done differently.

Wish I had some people to rub shoulders with after work who work in my field. There's only 1 other developer here besides me. Any ideas how I might dig some people up, some fellow developers to hang out with?

philcart SSC-Forever Points: 47794 More actions · Answer 3

Greg

Where do you hail from?

You might have noticed the links in my signature, that's a start if you're an Aussie

Otherwise checkout MSDN Connections, they have a list of groups there. Also, http://www.sqlpass.org maintains a user group list.

--------------------
Colt 45 - the original point and click interface

Frank Kalis SSC Guru Points: 111183 More actions · Answer 4

Looking for best practices from a developer's perspective. To much code to write & not enough reading time. I hate discovering a week after I've finished a project that something I did should have been done differently.

Phill already mentioned the Best Practice Analyzer, which is probably more focused on development than administration. Definitely worth a try and a good start anyway. Also, take your time and look through the links I've mentioned in your other thread. Andy Warren did also some articles on Best practice.

However, the smartest thing, IMHO, is to ask a question here when you are uncertain. It's mostly also a huge time saver.

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

Jim P. SSCrazy Eights Points: 8725 More actions · Answer 5

Welcome to the asylum. You found this place sooner than I did.

The big one I see in unsnarling your databases is knowing the business and business model. IMHO, that is the key to success.

I maintain 25-30 databases across 2 servers plus a recovery server and test server. I know which databases need full or simple recovery. What needs archived for audit purposes, etc. What apps access the server and how.

Once you get that down then the maint plans become obvious. And be careful about running down the former DBA. You don't know who liked him/her. Also walking in and announcing a new sheriff is in town can cause problems.

That's just my $0.02.

----------------
Jim P.

A little bit of this and a little byte of that can cause bloatware.

Greg Norris-214114 SSC Eights! Points: 888 More actions · Answer 6

In answer to Phil's question,

I just moved from Missouri to Georgia (both USA) a month ago to launch my IT career with a small software company. I'm a developer by title, but in a company with 6 employees (only 2 in IT), there's no telling what hat I might be wearing in the coming months.

One of these days I hope to visit Australia, but it won't be anytime soon.

Thanks for all the tips & info. This is a fantastic forum! I've been using Tech-Tips for several years while going to school and it has been great, but when it comes to SQL Server, this forum is in a league by itself.

Thanks again,

Greg