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

Guidance Expand / Collapse
Author
Message
Posted Monday, August 19, 2013 8:57 PM


SSC-Dedicated

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

Group: Administrators
Last Login: Today @ 11:38 AM
Points: 33,165, Visits: 15,298
Comments posted to this topic are about the item Guidance






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1486090
Posted Tuesday, August 20, 2013 9:40 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Thursday, August 7, 2014 3:34 PM
Points: 2,282, Visits: 1,341
Steve Jones - SSC Editor (8/19/2013)SQL Server is complex. We can't easily reduce the solutions to problems to a set of rigid protocols that ensure optimal performance. If we could, there truly wouldn't be as much of a need for DBAs as there is.


Good read and to the point. I would add one thing. Since SQL Server is complex and the configuration etc of the product depends ... There is very little chance that the SQL configuration out of the box will be optimal for most if any applications/systems. Due to both the complexity of the product and the business practices there is a high probability that the simple, default, generic configuration will need to be significantly altered to optimize the services needed.



Not all gray hairs are Dinosaurs!
Post #1486330
Posted Tuesday, August 20, 2013 4:04 PM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Today @ 12:39 PM
Points: 624, Visits: 2,145
Miles Neale (8/20/2013)
Good read and to the point. I would add one thing. Since SQL Server is complex and the configuration etc of the product depends ... There is very little chance that the SQL configuration out of the box will be optimal for most if any applications/systems. Due to both the complexity of the product and the business practices there is a high probability that the simple, default, generic configuration will need to be significantly altered to optimize the services needed.


There is one configuration change that I always make immediately after I install SQL Server, and advise everyone else to do too. That is turn off Named Pipes. I don't know if they'll ever get rid of it, but I think it is the most useless thing M$ ever did.




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

A little bit of this and a little byte of that can cause bloatware.
Post #1486466
Posted Wednesday, August 21, 2013 7:21 AM


SSC-Dedicated

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

Group: Administrators
Last Login: Today @ 11:38 AM
Points: 33,165, Visits: 15,298
Jim P. (8/20/2013)

There is one configuration change that I always make immediately after I install SQL Server, and advise everyone else to do too. That is turn off Named Pipes. I don't know if they'll ever get rid of it, but I think it is the most useless thing M$ ever did.


LOL, named pipes used to be important. Back when I started, we weren't running TCP/IP and named pipes worked well to allow communication.

It is archaic and unneeded now, but it served a purpose at a time.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1486696
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse