Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

SQLServerCentral Best Practices Clinic: Part 1 Expand / Collapse
Author
Message
Posted Monday, March 7, 2011 12:00 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, October 16, 2014 10:06 AM
Points: 176, Visits: 728
Comments posted to this topic are about the item SQLServerCentral Best Practices Clinic: Part 1

Brad M. McGehee
DBA
Post #1073964
Posted Monday, March 7, 2011 8:55 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, October 16, 2014 10:06 AM
Points: 176, Visits: 728
Please add your feedback below about the SSC server configuration. SQL Monitor on the two clustered nodes has been upgraded to Version 2.2, the latest release of SQL Monitor.

Brad M. McGehee
DBA
Post #1074223
Posted Monday, March 7, 2011 8:58 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Saturday, December 20, 2014 3:11 PM
Points: 31,368, Visits: 15,837
One quick note: we use Standard Edition.

I was hoping to use Resource Governor to tune the newsletter load and limit the impact of that process on our servers, but it's not available in Standard or Workgroup editions.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1074225
Posted Monday, March 7, 2011 9:07 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, December 23, 2014 6:54 AM
Points: 75, Visits: 154
several of your databases are set to auto grow the data file in increments of 1mb. I wouldn't use that setting for any database, i prefer to use percentages, usually 10%. It really doesn't make sense though for the SQLServerCentral database, due to its larger size.
Post #1074232
Posted Monday, March 7, 2011 9:34 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, October 16, 2014 10:06 AM
Points: 176, Visits: 728
Chris Golla (3/7/2011)
several of your databases are set to auto grow the data file in increments of 1mb. I wouldn't use that setting for any database, i prefer to use percentages, usually 10%. It really doesn't make sense though for the SQLServerCentral database, due to its larger size.


I agree that the default value of 1MB autogrowth is a poor choice, but I prefer to use a larger fixed amount rather than a percentage, as percentages don't always act as you expect. For example, if I set a percentage of 10%, 10% of 1GB is a lot different of 10% of 1TB. Thus, I prefer to pick a fixed amount that makes sense for the existing size of the database. Ideally though, I prefer to proactively manage the size my MDFs and LDFs so that autogrowth doesn't have to kick in at all. I prefer to use autogrowth only to cover unexpected growth spurts I had not planned on.


Brad M. McGehee
DBA
Post #1074261
Posted Monday, March 7, 2011 9:43 AM


Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, November 25, 2014 3:52 PM
Points: 5, Visits: 57
The main interesting thing I saw is that you are on Build 2714, which is fairly old (SP1 CU2). I would want to get SP2 CU2, Build 4272 installed. If you could run my full set of diagnostic queries, I would know a lot more...

Do you have "Optimize for ad-hoc workloads" enabled for the instance?
Post #1074272
Posted Monday, March 7, 2011 9:58 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, October 16, 2014 10:06 AM
Points: 176, Visits: 728
GlennBerry (3/7/2011)
The main interesting thing I saw is that you are on Build 2714, which is fairly old (SP1 CU2). I would want to get SP2 CU2, Build 4272 installed. If you could run my full set of diagnostic queries, I would know a lot more...

Do you have "Optimize for ad-hoc workloads" enabled for the instance?


In this installement, we are only focusing on the properties revealed by SQL Monitor. I think running your diagnostic queries would work great for another part of this article series. I'll get back with you when we are ready to do this.


Brad M. McGehee
DBA
Post #1074286
Posted Monday, March 7, 2011 10:59 AM


Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, November 25, 2014 3:52 PM
Points: 5, Visits: 57
It seems like you are getting regular CPU spikes to 100% every night at about midnight. Is that when your full backups occur? Are you using 3rd party backup compression that has an adjustable compression ratio?

It seems like your page splits are a little high at the instance level.
Post #1074324
Posted Monday, March 7, 2011 7:08 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, December 15, 2014 10:56 AM
Points: 1,945, Visits: 2,064
Besides the obvious filegrowth setting issues mentioned previously, one thing I found was there was not much use of filegroups. One of the things I like to do is have all of my nonclustered indexes on a separate filegroup that is located on a different I/O path.
Post #1074566
Posted Tuesday, March 8, 2011 7:51 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, October 16, 2014 10:06 AM
Points: 176, Visits: 728
tgarland (3/7/2011)
Besides the obvious filegrowth setting issues mentioned previously, one thing I found was there was not much use of filegroups. One of the things I like to do is have all of my nonclustered indexes on a separate filegroup that is located on a different I/O path.


Good point. This option wasn't chosen for two reasons. First, the servers are hosted, and our I/O options weren't wide. Second, the activity on the server is not really that great, relatively speaking, necessitating the need for such tweaking. Of course, there are other performance issues, but separating the nonclustered indexes wouldn't have helped much to alleviate them. We will talk about what is causing the performance problems in a later article.


Brad M. McGehee
DBA
Post #1074816
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse