I have a 2 part question about adding a new 'named' Virtual Server to an existing Clustered SQL Server 2000 install.
I have a 2 node MSCS Cluster (WIN2K advanced Server sp4) with a default SQL Server instance. This has been in production and working fine. I created a new Cluster resource and reran SQL Server 2000 ENT setup and added a second Virtual SQL Server (named instance). After many problems, finally got the second Server installed. Now I have 2 SQL Server instances in the Cluster - from what I understand, you can have up to 16, each seperate installs with seperate Cluster resources.
Thus the problem:
For the Second Instance, I have specific instructions from the Applications vendor on how to install SQL Server to work with their APP. I need install SQL Server WITHOUT the Full Text Search component and WITH a specific Server Collation (Binary order for use with the 850 Multilingual character set). (I have done this same setup on standalone SQL Server installations for this APP and they have gone smooth).
When I installed the new Virtual 'named' instance in my Cluster, I Could NOT 'DESELECT' Full Text Search when I choose Custom install.. it does not appear as an option?
Also, I chose the "Binary order for use with the 850 Multilingual character set" during the installation, but that is not the Server Collation that is installed...
I have already installed SP3 for SQL Server against the Virtual Server on this Cluster, as well as a HotFix... and Now I'm thinking I need to rerun the SQL Server installation, uninstall the second server and reinstall to see if I can fix the 'Collation problem' .. but I'm not sure if this is the right course of action.
Does anyone know why I cannot 'deselect' Full text search component at install, and any ideas why it did not install with the SQL Server Collation that I specified at install??are you seeing the same collation on the named instance as the collation on the default instance? did you check the install log for the named instance? any clues there? event viewer system and app logs?|||Originally posted by ms_sql_dba
are you seeing the same collation on the named instance as the collation on the default instance? did you check the install log for the named instance? any clues there? event viewer system and app logs?
Yes. it DOES have the same collation as the default instance!!! I had already checked the install logs and I did not see anything unusual. I DO see where it set the Server Collation in the install log, which is the sme collation as the default (original) server. I don't understand why if, in this kind of configuration you can have up to 16 SQL servers, why it would pull configuration settings from the first install??
Microsoft Knowledge Base Article - 298568 references a rebuildm.exe utility which will allow you to rebuild the master database with the correct collation.. I found a rebuildm.exe and rebuildm.rll in the 'program files' folder for the original 'default' install, but I cannot find these files in the second 'virtual server' program files folder.
When running the virtual server installation, it seemed pretty straight-forward. the only settings I changed were collation and the path for the program and data files (i put the data files on my new cluster resource drive) and I put the program files on the 'D' drive which is a fixed drive found on both nodes. it wanted to install the program files on the same drive as the original 'default' server. maybe I shouldn't have changed the program files setting??
I'm stumped!!!
