![]() Under “Install Instructions” find the section that is shown in the screenshot below. Skip this if you had the SQL Server Native Client as an option: The easiest way to install this is by downloading it from the Microsoft website. Note: You will not have this option if SQL was installed on a separate server. Go to Start -> Administrative Tools -> and open ODBC Data Sources (64 Bit):Ĭlick on the System DSN tab and click Add:Ĭlick on SQL Server Native Client 11.0 and click Finish. Next parts are to be done on your vCenter server. Now we get to setup the ODBC connection for vCenter to use. It is a good time to reboot your SQL server for the settings to take effect. Make sure to change Enabled to Yes and TCP Dynamic Ports to 0 (zero). Right click on TCP/IP and click Properties. Skip this part if vCenter and SQL are running on the same box: You will need to modify the TCP/IP settings for SQL. Open the SQL Server Configuration Manager, go to SQL Server Network Configuration, then Protocols for MSSQLSERVER. I will give SQL 2 GB which leaves 2 GB for the OS. I am running this in my home lab on a VM with 4 GB of RAM. On the Memory page we will want to limit the amount of memory SQL can use. ![]() Click Ok:īefore we leave SQL Management Studio as a best practice right click your SQL server name and go to Properties: Go to the Options page and change the Recovery model to Simple. Next right click on your VCDB database and go to Properties: You will now have a VCDB DB under Databases. You should receive a message saying “Command(s) completed successfully. Make sure it matches all the way through the script.Ĭlick Execute.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |