SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Pre Check List for 64 BIT SQL Server 2008 Cluster Installation


Pre Check List for 64 BIT SQL Server 2008 Cluster Installation

Author
Message
Rudy Panigas
Rudy Panigas
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1722 Visits: 1315
Comments posted to this topic are about the item Pre Check List for 64 BIT SQL Server 2008 Cluster Installation



Harold Buckner
Harold Buckner
Right there with Babe
Right there with Babe (745 reputation)Right there with Babe (745 reputation)Right there with Babe (745 reputation)Right there with Babe (745 reputation)Right there with Babe (745 reputation)Right there with Babe (745 reputation)Right there with Babe (745 reputation)Right there with Babe (745 reputation)

Group: General Forum Members
Points: 745 Visits: 420
Just a quick question on your comment

"This virtual NIC is not liked by the SQL Server installation, which will complain and fail. You will need to "unteam" the NICs via the HP software and then you can disable or assign another IP address to them."

I keep reading about this issue over and over on the blogs but have been running virtual nics for years with my cluster. What sort of problems does SQL Server have with this setup so that I can watch out for it or not use when we rebuild our next one?

Thanks
Harold
Rudy Panigas
Rudy Panigas
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1722 Visits: 1315
Hello,

Good question and I too had asked that during my first install. Basically it comes down to NIC(s) that are not used. If there is a NIC installed (virtual or physical) and it is not used (configured and in use) then the installation will have a problem.

It appears that the Windows 2008 does not understand why you would have a NIC(s) that is installed but not in use.

Finally, if you are using a "teamed" configuration (a second NIC to handle a failure of the first NIC) then you are recommended to "unteam" then. Once your install is completed you can "re team" them.

Hope this helps,

Rudy



Curtis Smith
Curtis Smith
Mr or Mrs. 500
Mr or Mrs. 500 (583 reputation)Mr or Mrs. 500 (583 reputation)Mr or Mrs. 500 (583 reputation)Mr or Mrs. 500 (583 reputation)Mr or Mrs. 500 (583 reputation)Mr or Mrs. 500 (583 reputation)Mr or Mrs. 500 (583 reputation)Mr or Mrs. 500 (583 reputation)

Group: General Forum Members
Points: 583 Visits: 239
Another issue that is somewhat related to this is installing on Server 2008 R2, which requires the installation to be slipstreamed. Its best to check before running the installation. http://support.microsoft.com/kb/955725




Curtis Smith
SQL Server DBA
Well in worked in Theory ...
S. Kusen
S. Kusen
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2202 Visits: 1117
We have teamed NIC's on just about all of our clusters where I work, and I personally haven't experienced any problems leaving them teamed for the SQL install. I've only done one Server 2008 R2 cluster install, but had no issues with the install, and connectivity is fine. The one issue we did find was a DNS message, but that was coming up because we manage our DNS system with QIP, and there is a fix from MS posted to prevent that message from appearing. Unfortunately, I can't locate the article... and I forget the exact message, but it was unrelated to having the NIC's teamed.

Great article though!!

Regards,
Steve
Rudy Panigas
Rudy Panigas
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1722 Visits: 1315
Thanks for the additional info. Looks like SQL 2008R2 has fixed this issue but it does exist with SQL 2008. I have not installed SQL 2008 R2 as that's for another article.

Thanks again,

Rudy



SQLRNNR
SQLRNNR
SSC-Forever
SSC-Forever (49K reputation)SSC-Forever (49K reputation)SSC-Forever (49K reputation)SSC-Forever (49K reputation)SSC-Forever (49K reputation)SSC-Forever (49K reputation)SSC-Forever (49K reputation)SSC-Forever (49K reputation)

Group: General Forum Members
Points: 49355 Visits: 18570
Nice article



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Harold Buckner
Harold Buckner
Right there with Babe
Right there with Babe (745 reputation)Right there with Babe (745 reputation)Right there with Babe (745 reputation)Right there with Babe (745 reputation)Right there with Babe (745 reputation)Right there with Babe (745 reputation)Right there with Babe (745 reputation)Right there with Babe (745 reputation)

Group: General Forum Members
Points: 745 Visits: 420
Thanks for all the great info and the replys.
EdVassie
EdVassie
SSCrazy Eights
SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)

Group: General Forum Members
Points: 9381 Visits: 3884
I think this is a very helpful article. There is one aspect that many people take for granted, but I think should get challenged more, even if the challenge can be contentious...

I have seen advice from some tuning experts that turning off paging on a 64-bit machine can be best for performance. This is achieved by specifying a custom page file size of zero MB.

If you do this you will not get a system dump if Windows fails. Therefore you need to balance the risk of this with the inconvenience of making a page file available if you have a failure that needs a memory dump.

The advice from NT4 days that the page file shold be 1.5 time the size of physical memory is now obsolete. The 1.5 ratio is only needed if you want to dump all memory on the box. If you have a 128GB box, then Microsoft will never need a 192 GB dump to disgnose the problem you have, so why set your page file to 192 GB? If you do decide to have a 192 GB page file, you also need to work out how you will get a 192 GB dump to Microsoft.

IMHO that optimum size page file for a 64-bit box is zero MB, and the maximum size is the whatever is needed for a snap dump (400MB for W2008 R2).

Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 14 Mar 2017: now over 40,000 downloads.Disclaimer: All information provided is a personal opinion that may not match reality.Quote: When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist. - Archbishop Hélder Câmara
tomko
tomko
Grasshopper
Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)

Group: General Forum Members
Points: 22 Visits: 50
Good article, as it addresses many issues with a WIn2008 and SQL2008 cluster on the install.

But no antivirus? You need to tune the antivirus correctly for a SQL system but to recommend no AV makes no sense at all. Are you going to scan your system every day? With no AV, you better be scanning it.



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