Comments on: The Accidental DBA (Day 4 of 30): SQL Server Installation and Configuration Best Practices

By: Gaoussou

Gaoussou — Tue, 13 Dec 2016 03:43:07 +0000

When working with firewall setting for Sql, I like to go by port number rather than the application. If you create a rule for sqlservr.exe, I believe it will be only for one instance. Here is my quick inbound rules for SQL instances:
Open TCP port for 1433 and 1434 when only using a default instance. if you have a named instance, also open UDP port for 1434 and always make sure Sql Browser is running. Of course if using more SQL features, make sure to open the respective ports.
Thanks.

By: Glenn Berry

Glenn Berry — Tue, 03 May 2016 19:19:22 +0000

In reply to Mirza. Usually, opening ports 1433 and 1434 are all you need or want to do.

By: Mirza

Mirza — Tue, 03 May 2016 17:47:56 +0000

Questions on Firewalls.
1. Do we need to allow specifically the sqlservr.exe in firewall as the following article is talking about: http://bit.ly/1W6SJh9

is that a good practice?

2. Do we need to specifically allow 1433 in firewall?
3. I think we should allow port 1434 for Dedicated Admin Connections in firewall. Please correct me if I am wrong here.

Thanks.

By: Glenn Berry

Glenn Berry — Mon, 17 Aug 2015 19:41:35 +0000

In reply to Mark. It is actually pretty common (and I think it is a good idea) to make the Windows Page File pretty small, such as 4-6GB, and fixed in size. With SQL Server, if you are ever using the Windows Page File, that means you are under severe external memory pressure, and your performance is going to be very, very bad.

By: Mark

Mark — Fri, 14 Aug 2015 19:04:33 +0000

Any best practice pointers on figuring out the best page file size for a 64 bit server with (larger) memory sizes? I see quite different recommendations – but if I have SQL max memory set to something (4 to 8 gig less) then memory, and the appropriate settings so SQL can lock pages, am I correct that the most I’d for a swap file is the memory (or 1.5x?) reserved for the OS?

(and given no other processes other then SQL components…how much should be reserved?)

thanks!

By: Glenn Berry

Glenn Berry — Wed, 03 Jun 2015 21:28:35 +0000

In reply to Diane Sithoo. Especially when it comes to SPs and CUs, I think your idea of patching the subscriber first (especially when you have multiple subscribers) makes a lot of sense. If the SP or CU causes an issue (which is actually pretty rare), then you will have only affected that one subscriber, which would cause less of an impact than if you caused a problem with the publisher or distributor.

By: Diane Sithoo

Diane Sithoo — Wed, 03 Jun 2015 17:00:19 +0000

Hi Glenn, Could you expand on hybrid deployment best practices for applying patches, and specifically SPs and CUs? I’m trying to find some clear references as to why you should apply them to distributors first, publishers second, and subscribers third in a replication topology. I know that’s best practice, but in our organization, we have many subscribers that are used for load-balancing, and it seems less risky to apply patches to one first and if it bites the dust, we have many more that carry the load. Is there a risk to the publisher and/or distributor?

I know that if the replication components are affected, there could be problems with compatibility, and that if it fails on a subscriber then subscriptions may have to be reinitialized. What if the SP/CU has no references to replication? Have there been actual examples of this in practice?

By: Glenn Berry

Glenn Berry — Mon, 20 Apr 2015 14:02:58 +0000

In reply to Tom Strike. That is just a typo. Microsoft Update is a superset of Windows Update.

By: Tom Strike

Tom Strike — Sun, 19 Apr 2015 20:44:17 +0000

I don’t understand this, am I missing something? Microsoft Update is a superset of Microsoft Update?

“You also want to make sure that Windows Server 2012 has been fully patched, using Microsoft Update (which is a superset of Microsoft Update).”

By: Mark V

Mark V — Tue, 02 Jul 2013 03:53:47 +0000

Hi Glenn,

Would you elaborate on your recommendation to install CUs by default?

Up until now, I thought SPs are tested more thoroughly by Microsoft and you really don’t want half tested changes running on Prod.

Thank you!
Mark V